Semantic model of everything recorded with ur-url combination identity-identifier-addressing-indexing method, means, and apparatus

ABSTRACT

A computer program product embodied on a non-transitory computer readable storage medium, comprising non-transitory computer executable program code configured to perform the steps of: receiving a representation of an unlabeled event; labeling the unlabeled event according to a unitary relative event ontology; and storing the labeled event in the computer readable storage medium. The unitary relative event ontology can comprise an information description vector comprising a plurality of ontological primitives, and the plurality of ontological primitives can comprise a point description element, a reference-body description element, an observer description element, a position description element, a scene description element, and a specification description element.

RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent applicationSer. No. 12/802,058 filed on May 28, 2010, which is a continuation ofU.S. patent application Ser. No. 10/231,085 filed on Aug. 29, 2002,which claims priority to U.S. Provisional Application No. 60/315,923filed on Aug. 31, 2001, the contents of which are incorporated herein byreference in their entireties.

TECHNICAL FIELD

The present invention relates generally to event identity, whereeverything is defined as an event. The general field is event identityas applied in the context of symbolic representation of resources in aglobal network of information and communication systems. The morespecific field is event identity as a control element in lists, tables,and relational database systems, and as essential network informationinfrastructure. The present invention is a Semantic Model of EverythingRecorded according to FIG. 1, hereinafter named and referred to assimply Model of Everything, where everything recorded comprises claimsof event description.

Analog Context

Reality is everything real. Real is what's known and agreed to. Thepublic domain represents the record of what's known and agreed to.Assertions are claims made by people about themselves and theirproperty. “Facts” are claims authenticated by credible witness. Ideas,discoveries, theories, principles, and other non-objective things in|EVERYTHING|, as well as real and personal property, are circumscribedby agreements about ownership in the form of authenticated claims byauthenticated maker-owners. Individuals and businesses voluntarilyrecord claims of ownership because that's the information they wantpeople to know.

Thus, the terms reality, everything real, and |EVERYTHING|, for thepurposes of a Model of Everything, are defined as the sum total of allthe agreements we have about it. The scope of a Model of Everything isbounded by the evolving analog (real world) agreements that comprise oursocial, economic, and political compacts captured and recorded inproceedings, publications, libraries, journals, files, folders,computers, and media, all over the world.

This is the historical record of everything real. This is the scope ofthe present invention, which usefully identifies, differentiates, andcorrelates identity for all events, including all property “objects” andall ownership “assertions” with one common reference architecture. Othermethods are limited to identifying many events.

Unitary Reference Architecture is at the same time a combinationidentity-identifier-addressing-indexing method and a new IT architecturefor the current generation of information networks. Additionally, it isa next generation unitary programming syntax method. Plus, it is afuture generation representational medium for depicting, manipulating,directing, sequencing, synthesizing and controlling information eventsin digital environments.

It will be made apparent that the present invention meets widespreaddemand for a comprehensive solution to long-standing problems consideredunsolvable by experts who have tried and failed. It also reveals andremedies an unrecognized defect, and provides both the desired end andunexpected collateral results across the whole domain of informationsystems and application subsystems that use and depend on identity foressential operations.

Structural Context

What's information architecture? “At its most basic, informationarchitecture is the construction of a structure or the organization ofinformation. In a library, for example, information architecture is acombination of the catalog system and the physical design of thebuilding that holds the books. On the Web, information architecture is acombination of organizing a site's content into categories and creatingan interface to support those categories.”₃

Here's a definition from experts Rosenfeld and Morville from ArgusAssociates: “Information architecture involves the design oforganization, labeling, navigation, and searching systems to help peoplefind and manage information more successfully.”₄ Informationarchitecture is another term for the present invention's identityaddressing and indexing method.

According to Webster, a system is “a regularly interacting orinterdependent group of items forming a unified whole.”₅ In practice,“The System” is the set of regularly interacting and interdependentfederal, state, regional and local agreements we call our civil society.It's formalized as rules—laws, contracts, ordinances, covenants, norms,agreements, principles, values—the definitions about how we interact aseconomic beings. The rules we share are the reference architecture ofsociety. These agreements are captured in various analog media as files,records, microfiche, documents, books, text, graphics, and various listsand tables.

Technical Context

In computer science, a data structure is a particular way of storing andorganizing data in a computer so that it can be used efficiently. A datamodel represents semantic information associated with objects stored ina file system. Arrays are among the oldest and most important datastructures, and are used by almost every program. They are also used toimplement many other data structures, such as lists and strings. Theyeffectively exploit the addressing logic of computers. In most moderncomputers and many external storage devices, the memory is aone-dimensional array of words, whose indices are their addresses.Processors, especially vector processors, are often optimized for arrayoperations. In some cases, the term “vector” is used in computing torefer to an array, although tuples rather than vectors are morecorrectly the mathematical equivalent. Arrays are often used toimplement tables, especially lookup tables; the word table is sometimesused as a synonym of array. List and database size is limited by thequantity of available variables within the ID numbering system'snomenclature.

What makes a bunch of data “a system” is that it has at least one thingin common and at least one thing that's different. One way you keeptrack is by numbering the things, which meets the condition fordifference. There can't be two with the same ID number. If you have onelist with a number method, say one through ten, and another list with analpha method, ordered A to Z, and combine them, it's OK as long as allthe identifiers are unique. It's still a system, if the two lists havesomething else in common, maybe the purpose or owner or anything. Havinga field for unique identifiers in the first place can be the thing thetwo systems have in common.

The only mandatory field in a table is the identifier. The uniqueidentifier is usually the first column in a relational table orspreadsheet. Off the shelf programs like Excel and Lotus 1-2-3 havereference architecture that stipulates numbered rows and alpha columnswith unique identifiers for each cell made up of the referencecoordinates as a code: A1, B2 . . . conveniently built into the page forat-a-glance orientation. Having addresses for all the cells means youcan do things with individual data, as well as with groups, or columnsand rows of data. This kind of organization is the foundation ofinformation science because pretty much all of the information in theworld is part of some kind of list or table in some kind of file.

The easiest way to combine information in two old different systems isto make a new bigger file with both. This is called merging and thetechnical term is data integration. Regardless of whether your purposeis to upgrade old internal systems or to communicate with new externalsystems, if you want to integrate data, you have to design a newidentifier code that will ensure all the individual items in all thetables have unique identity in one combined system. Common fields, likename and address, are rarely unique. Interoperability is facilitated bycommon identity nomenclature. If you agree up front about the semanticarchitecture, you don't have costly conversion projects every time youadd another partner.

Integrated End-To-End Solution

The present invention's Unitary Technology delivers an end-to-endarchitecture for identifying, owning, naming, differentiating,representing, describing, depicting, illustrating, modeling, simulating,synthesizing, replicating, relating, connecting, associating, combining,merging, integrating, unifying, organizing, classifying, indexing,locating, addressing, positioning, routing, maintaining, storing,retrieving, finding, sharing, improving, sequencing, instructing,operating, manipulating, and controlling information events with oneapproach, one infrastructure, one architecture, one method, and oneprincipled basis—a singular solution.

Description of Related Art

The differences between the present invention and prior art lie insimple scope, as well as specific application. Digital Earth₁₆ is citedas a massive global initiative to create a digital linked network ofterrestrial data using digital mapping and locating technologies(GPS/Global Positioning System geospatial reference coordinates) torepresent the earth's geographical features. Their scope includes thespectrum of very large (oceans and continents) to very small (media richdescriptive meta data attached to a narrowly circumscribed area)phenomena. Digital Earth represents objects in a distributed network ofservers with multiple addressing methods.

The Universal Semantic World Wide Web₁₇ is a requirements description ofan ideal web representation. According to the World Wide WebConsortium's (W3C) “Principles of URI/ID Design,”₈ the key features ofan ideal Universal Resource Identifier (URI) are Uniqueness,Universality, Persistence, Scalability, Evolvability, Opacity, NoSide-effects, Global uniqueness, Optional sameness, FullyNon-dereferenceable, Infinite number of referential mints, Myriadinterchangeable code variations within same referential system.

Embodiments of the present invention meet these criteria. Furthermore,it demonstrates W3C ideal design principles, which are Simplicity,Modular Design, Tolerance, Decentralization, Test of IndependentInvention, and Principle of Least Power.

Embodiments of the present invention combine the content vision of thefirst with the semantic approach of the second.

BRIEF SUMMARY OF THE INVENTION

The present invention is made up of: a unitary information architecture,a method for self-minted self-service identity, a scalable businessprocess for integrating data from different tables and/or from differentsystems into one combined system, a method to organize everything, and asearch engine and directory to make it all accessible. There's also aprogramming process and language, a modeling medium, and a number ofinteresting applications that in further combination provide a newroadmap, a new on-ramp, and a new routing mechanism for commuters on theinformation super-highway.

Unitary Identity

Traditional object oriented approaches begin with objects as entitiesthat own properties, relations, and participation in events. Objects areaccumulated in functional databases where difference—more apparent thancommonality—drives an army of upgrade licenses marching side by side.The inventory control system has one kind of information, the humanresource system another, which may or may not match the resource pool inthe scheduling system, and there are often legacy data pockets thatdon't match anything.

In contrast, Unitary Technology starts with relativity and an eventorientation. Everything is an event. Events are entities that ownobjects. And makers own events and artifacts. The event of object,what's being recorded in the list, is a semantic representation ofeither original incept of the aggregation of constituents, thepreliminary definition in the system, or update—a change to any aspectof original condition.

Universal Referential—Uniform Resource Locators (UR-URL) compriserelative referential geocoordinates (XYZT). UR-URL provides one commontable field and one common nomenclature to describe the one thing thateverything has in common—incept. The field that unifies, butdifferentiates is XYZT/incept. It's already a unique name, if youstipulate both location and time in terms of referential relationshipand ownership. Ownership is the key to differentiating many claimssharing one event identity.

Independent Minting

With Unitary Technology, each system (internal and external) may betreated as a subsystem to the whole with addresses relative to any pointand scale. Reuse and integration are easy. Systems using differentreferences are easily converted to equivalency. Owners mint identifiers.Identifiers correspond to real objects, assertions, and artifacts,actual times and places. Longitude, latitude, and elevation coordinatescome in different varieties. E-Gov will likely apply some standardgeoreferencing convention for official use. Conversion formats andformulas will be bundled as plug-ins. It won't matter which standardreferences or syntax are used within any given system, what will matteris real-time agreement to protocols when two systems exchange data.

Unitary Ontology

Unitary ontology is fundamental technology. The following logicalstatement stipulates one super-ordinate unitary ontologicalarchitecture. Basis: Everything is an event. Objects are events.Assertions are events.

The terms Event Assertion and Event Object are defined as inclusive ofand synonymous with generally held top-level divisions of everything,i.e.: physical or non-physical, tangible or intangible, matter or mind,thing or concept, object or subject, property or agreement, phenomena ornoumena, and so forth. All other ontologies are by this definitionDerivative Ontologies.

All existing ontologies, taxonomies, and classification systems fallwithin their respective domains as either Event Assertions or EventObjects. Unitary Ontological Reference Architecture does not attempt tospecify variety or number of referential systems. Indeed, the functionof unitary ontology is to establish an all-inclusive framework withinwhich any number of classification systems and parameters may beemployed.

The secondary purpose of establishing one unitary ontological referencearchitecture is to usefully and universally categorize the domain[EVERYTHING] so as to make information accessible. The primary purposeof Unitary Ontological Reference Architecture is to show conclusiveevidence that the domain [EVERYTHING], as defined herein, and claimed bythe present invention, is indeed inclusive of everything. No othermethod claims all events, which if you agree with Einstein, iseverything. No other method claims all objects and all assertions, whichis everything if you use common non-relativistic definitions. Details ofUnitary Ontology Architecture are depicted in the several views of thedrawings.

Unitary Information Architecture

One information architecture doesn't mean all the information in theuniverse is contained in one place, on one server, of one type, in onelanguage, or one database. It means all the information everywhere canhave the same basic set of terms, the same system of identifiers, thesame organizing basis, and the same classification conventions so allthe information and communication events can be sensibly integrated forfast access by both users and agents, internally and with partners.Plus, common terms simplify multi-dimensional analysis across disparatedata sets.

Unitary Technology

Unitary Technology culminates the drive for information on demand with ablueprint for the ultimate resource—the present invention—onereferential system and Semantic Model of Everything Recorded.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

List of Figures

View I—Identity of Everything—Zero Dimension

FIG. 1 Everything

FIG. 2 Construction of Everything

FIG. 3 Deconstruction of Everything

FIG. 4 Dimension of Everything

FIG. 5 Extent of Everything

FIG. 6 Description of Everything

FIG. 7 Unitary Reference Architecture Components

FIG. 8 Alignment of Scope and Components

FIG. 9 Relation of Scope and Components

FIG. 10 Everything Components

FIG. 11 Unitary Reference Architecture Components

FIG. 12 UR-URL Identifier Method Components

View II—List of Everything—One Dimension

FIG. 13 List of Everything Components

FIG. 14 List View

FIG. 15 List With Prior Art Reference Architecture

FIG. 16 List With Unitary Reference Architecture

View III—Table of Everything—Two Dimensions

FIG. 17 Table of Everything Components

FIG. 18 Table View

FIG. 19 Table With Prior Art Reference Architecture

FIG. 20 Table With Unitary Reference Architecture

FIG. 21 Top-Level Ontology

FIG. 22 Event Ontology

FIG. 23 Relative Event Ontology

FIG. 24 Entity Ontology

FIG. 25 Object Ontology

FIG. 26 Ontology of Origination

FIG. 27 Ontology of Dimension

FIG. 28 Ontological Integration

FIG. 29 Dimensional Integration

FIG. 30 Alignment Between Primitive Terms

FIG. 31 Matrix of Ontological Terms

FIG. 32 Ontology of Everything

FIG. 33 Table With Unitary Resource Description Framework (RDF)

FIG. 34 Table With Extended Unitary Resource Description Framework (RDF)

FIG. 35 Table With Simple Unitary Resource Description Framework (RDF)

FIG. 36 Table With Unitary Reference Architecture, Ontology, (RDF),Hardware and Software

View IV—Database of Everything—Three Dimensions

FIG. 37 Database of Everything Components

FIG. 38 Database View

FIG. 39 Database With Prior Art Reference Architecture

FIG. 40 Database With Unitary Reference Architecture

FIG. 41 Database With Unitary Reference Architecture, Hardware andSoftware

View V—Platform for Everything—Four Dimensions

FIG. 42 Platform for Everything Components

FIG. 43 Platform View

FIG. 44 Identity Expressions

FIG. 45 Logical Expressions

FIG. 46 Correspondence Between Expressions

FIG. 47 Description Expressions

FIG. 48 Programmatic Expressions

FIG. 49 Diagrammatic Expressions

FIG. 50 Menu Expressions

FIG. 51 Prior Art Menu Synthesis and Simplification

FIG. 52 Simplified Menu Expressions

FIG. 53 Unitary Platform

FIG. 54 Current Embodiment Access Process

FIG. 55 Web Services Vendor Mint Access Process

FIG. 56 Worst Case Future Vendor Mint Access Process

FIG. 57 Present Invention Access Process

FIG. 58 Access Process Comparison

FIG. 59 Direct Ownership Process Components

FIG. 60 Intermediary Ownership Process Components

FIG. 61 Ownership Process Components Comparison

View VI—Web Portal to Everything—All Dimensions

FIG. 62 Web Portal to Everything Components

FIG. 63 Web Portal View

FIG. 64 Unitary Web Portal

FIG. 65 Sample Web Portal to Everything Page 1

FIG. 66 Sample Record 1

FIG. 67 Sample Record 2

FIG. 68 Sample Record 3

FIG. 69 Sample Record 4

FIG. 70 Sample Record 5

FIG. 71 Sample Record 6

FIG. 72 Sample Record 7

FIG. 73 Sample Record 8

FIG. 74 Sample Record 9

FIG. 75 Sample Record 10

FIG. 76 Sample Records Summarized

FIG. 77 Sample Web Portal to Everything Page 2

FIG. 78 Enterprise Record Examples

FIG. 79 Enterprise Record Example Detail

FIG. 80 Present Invention Part List Example

FIG. 81 Homepage 1

FIG. 82 Homepage 2

FIG. 83 Homepage 3

FIG. 84 Homepage 4

FIG. 85 Homepage 5

FIG. 86 Homepage 6

FIG. 87 Homepage 7

FIG. 88 Homepage 8

FIG. 89 Homepage 9

FIG. 90 Homepage 10

FIG. 91 Homepage 11

FIG. 92 Homepage 12

FIG. 93 Alignment Between Components and Component Parts of UnitaryReference Architecture

FIG. 94 Alignment Between Parts and Part Numbers of Unitary ReferenceArchitecture

FIG. 95 Model of Everything Apparatus

FIG. 96 Sample Embodiment

View VII—Event-Oriented View—Architectural Dimensions

FIG. 97 Unitary Object Identity Array

FIG. 98 Unitary Event Identity Array

FIG. 99 Unitary Ontological Architecture

FIG. 100 Unitary Apparatus Structure

FIG. 101 Unitary Event RDF Architecture

FIG. 102 Comparison With Common Architectures

FIG. 103 Integration With Common Architectures

FIG. 104 Event Oriented Semantic Structure Illustrated

FIG. 105 Enterprise Information Asset Embodiments

FIG. 106 Enterprise Information Asset Ownership

FIG. 107 Sample Enterprise Information Asset Functions

FIG. 108 Enterprise Information Asset Management

FIG. 109 Comparison Between Webs

FIG. 110 Unitary Semantic Web

FIG. 111 Block Diagram of Computing Module

FIG. 112 Block Diagram of Labeling Process

FIG. 113 Sample Listings of Claims to Event Ownership

FIG. 114 Unitary Tools

FIG. 115 Concept Map

LIST OF TABLES

Table 1 Alignment Between Dimensional Views, Figures, Parts, andNumbering Nomenclature

Table 2 Sample Event Function Set Options

Table 3 MS Office Product Main Menu Examples—One Hundred and Two Objects

Table 4 Main Menu Synthesis—Twenty-Five Objects

Table 5 Sample Unitary Main Menu Optional Arrangements

Table 6 Unitary Terms of Description

DESCRIPTIONS

The present invention is a semantic information Model of Everything1000. Drawings illustrate the deconstruction of the conceptualsingularity “everything” through successive dimensional views ofcomponents and parts in order to demonstrate claims to universality:“infinitely extensible” and “universally applicable” and “everything inone system and all systems in one system”—that “everything” really is|EVERYTHING| recordable. Universality is made apparent in figures whichdefine what everything is, and show that everything:

-   -   1. can be scientifically identified, differentiated, and        integrated with UR-URL Identifier Method 101    -   2. can be versionalized by dimension with Unitary Infrastructure        200    -   3. can be grouped and classified with Unitary Ontology        Architecture 300    -   4. can be scientifically described with six universal terms of        Unitary Resource Description Framework 400    -   5. can be operationalized with Unitary Process Architecture 500    -   6. can be packaged and delivered with Unitary Apparatus 600

At one end of the spectrum, everything is one thing—one whole. At theother, everything is an exponentially huge quantity of quantum particlesin various arrangements and versions. There are many ways to systematizeeverything, and many ways to order explanations and images. To establishand maintain coherence throughout the many figures necessary for aslarge a subject as |EVERYTHING|, drawings are grouped in six dimensionalviews. Six high-level components shown in FIG. 1 correlate by dimensionas listed in Table 1. Sub-part numbers correlate to components and are,with a few exceptions, coded with the view identity (1, 2, 3, 4, 5, or6) as the last digit of the part number.

TABLE 1 Alignment Between Dimensional Views, Figures, Parts, andNumbering Nomenclature DIMENSIONAL SUB- FIGURE # VIEW COMPONENT PART #PART # FIGS. 1-12 0-D Identity Unitary Reference 100 100's ArchitectureFIGS. 13-16 1-D Unitary 200 200's Information Infrastructure FIGS. 17-362-D Object Unitary Ontology 300 300's Architecture FIGS. 37-41 3-DSystem Unitary RDF 400 400's FIGS. 42-61 4-D Process Unitary Process 500500's Architecture FIGS. 62-92 All-D Unitary Apparatus 600 600'sUnification

The next four figures show additional big-picture views of the wholeorganizational structure. FIG. 93 Alignment Between Component Parts ofUnitary Reference Architecture shows “parts added” with each successivehigher order component; FIG. 94 Alignment Between Part Numbers ofUnitary Reference Architecture, shows relationships betweensub-structures; FIG. 95 Model of Everything Apparatus Reference showsall the apparatus parts in one drawing; and FIG. 96 depicts a sampleembodiment. The final figures represent event-oriented architecturalviews.

I Identity of Everything View—Zero Dimension

FIG. 1 Everything

Everything, also referred to in absolute brackets |EVERYTHING|, is not apart or a component. Everything is the analog original that Model ofEverything 1000 is a model “of”.

Model of Everything 1000 has foundation in Principle 1.1, a term whichstands for the principle of unity on which the present invention rests,and the principles combined to make the present invention. Old analogprinciples of relativity are combined with old and new principles ofinformation science and applied in a new context of event identityarchitecture. Resultant is further combined with old analog principlesof private ownership and old principles of citizenship in a newuniversal identity architecture—the present invention—method, means, andapparatus for identifying, describing, and locating information eventsand information resources, with the unique feature of universalextensibility across the domain of |EVERYTHING|recordable, defined onPage 2 [0003], “Analog Context”, and again as follows:

-   -   Everything₂    -   1a: all that exists    -   1b: all that relates to the subject    -   2: every member or individual component of    -   3: the whole number or sum of    -   All₂    -   1a: the whole amount or quantity of    -   1b: as much as possible    -   2: every member or individual component of    -   3: the whole number or sum of    -   4: every    -   Reality₂    -   1: the quality or state of being real    -   2a (1): a real event, entity, or state of affairs        -   (2): the totality of real things and    -   2b something that is neither derivative nor dependent but exists        necessarily—in reality: in actual fact    -   Model₂    -   2: copy, image    -   4: a miniature representation of something; also: a pattern of        something to be made;    -   7: archetype;    -   10b: a type or design of product;    -   12: a system of postulates, data, and inferences presented as a        mathematical description of an entity or state of affairs.

Per above definitions, the present invention's Model of Everything 1000is at the same time a “semantic copy” of our analog system, a“miniature” digitized information version of analog known and claimedreality, a “pattern” to build modular integrateable systems, atechnology “product”, and “a system of postulates, data, and inferencespresented as a mathematical description of [everything],” where the term“mathematical description” in elemental form is comprised of a referencenumber (a unique identifier) and name (alpha and/or numeric identitycharacters/symbols) for each thing.

|EVERYTHING| is taken to mean everything known, specifically all knownreality as captured in analog and digital event records of event inceptclaims made by owners-makers-discoverers-originators in a distributednetwork of information system resources maintained in various storagemedia worldwide. The present invention's identifier method, UR-URL 101,is based on the discovery that relative referential geotemporalcoordinates, applied as unique identifiers to event claims in a systemof ownership that corresponds with analog principles of privateownership and citizenship, make possible the construction of a Model ofEverything 1000. As noted in other sections of the presentspecification, relative referential geotemporal coordinates may beinfinitely extended; relative referential geotemporal coordinates may beassociated with objective things; and, relative referential geotemporalcoordinates may be associated with maker-owner-discoverers at eventincept. What's yet to demonstrate is that“everything”=|EVERYTHING|—which will be made apparent in figures.

Figures are best understood as a multi-assembly bill of materials.Components, sub-components, and parts are arranged in tree-form and readas “goes into” charts—what's below “goes into” what's above. Conversely,what's above is “made up of” what's below.

FIG. 1 Everything depicts the structure of |EVERYTHING| as high-levelcomponents of the present invention, Model of Everything With UR-URLCombination Identity, Identifier, Addressing, and Indexing Method,Means, and Apparatus 1000, also referred to in embodiment Model ofEverything 1000. FIG. 1 provides a reference map for the overallarchitecture of Model of Everything 1000. Model of Everything 1000 ismade up of six components: Unitary Reference Architecture 100, UnitaryInfrastructure 200, Unitary Ontology Architecture 300, Unitary ResourceDescription Framework (RDF) 400, Unitary Process Architecture 500, andUnitary Apparatus 600. Components with sub-components and parts areindividually discussed in figures that follow.

FIG. 2 Construction of Everything

FIG. 2 depicts Levels of Abstraction 202.2, which is a sub-component ofDimension 202—shown as a component of Unitary Infrastructure 200 inFIG. 1. Parts of Levels of Abstraction 202.2 are conceptual dimensionsof everything;

-   -   202.2.1 Explication    -   202.2.2 Aggregation    -   202.2.3 Organization    -   406.3 Integration    -   202.2.4 Synthesis    -   202.2.5 Resolution    -   202.2.6 Unification

To understand what anything is made of, Levels of Abstraction 201.2provide iterative process steps which may be employed top-down orbottoms up, or from any level up or down. By starting with a whole, andusing a top-down approach, successive divisions lead to enumeration ofindividual elements. Conversely, starting with individual elements and abottoms-up approach, systems are created through successive combinationsuntil the final duality is resolved, and the whole circumscribed.

FIG. 3 Deconstruction of Everything

Levels of Abstraction 202.2 are used to think about what |EVERYTHING| ismade of. It would be very difficult to start at the bottom and listeverything without thinking in kinds. It would be impossible to know ifeach thing was represented without using kinds, but it would also bevery difficult to list every kind without thinking in systems. Andstill, there is no assurance that one system or another has not beenomitted altogether, so a top-down approach is used to deconstructeverything.

Starting at the top, the question is, what is the system identity of themodel? What is the “original” a system “of”? According to Relativity 302everything is an Event 301.2, and each thing is an Event 301.2. Model ofEverything 1000 is a model of All Events 201.6 in everything.

The next question is, what are labels for the top two or three maingroupings in everything, such that there are no elements not in agrouping? Animal-vegetable-mineral is a common way people think abouteverything. More common is physical-abstract, which takes into accountthe domain of ideas.

FIG. 3 depicts everything as a continuum with All Events 201.6 in thecenter at the Integration 406.3 dimensional level. All Events 201.6represents intersection of physical and abstract, with Mountains ofMatter 201.1.7 at one extreme on top of Icebergs of Ideas 201.1.8 at theother. Everything known is a lot of things and a lot of information. Buteverything known is either physical or abstract and nothing known is notphysical or abstract. At this first stage of deconstruction, theobjective version of the model includes everything.

FIG. 4 Dimension of Everything

Then, Levels of Abstraction 202.2 are also used to think about whatMountains of Matter 201.1.7 and Icebergs of ideas 201.1.8 are made upof. Mountains of Matter 201.1.7, taken as a whole, comprise Object ofEverything 201.1.6. That is all of physical reality.

What are labels for the top groupings in physical reality? Physicalreality is organized in systems, and systems of systems. Domain Objects201.1.5 is an inclusive term for “systems of systems” and Event SystemObject 201.1.4 is a label that applies to systems, which are collectionsof things or ideas cohered by common group label.

Everything could be divided into successive domain slices, but at thisstage of deconstruction the names and knowledge arenas don't matter.What's needed now are terms that generalize the “kinds” of objects thatform each level's divisions of everything. Event Domain Objects 201.1.5and Event System Objects 201.1.4 apply.

At the center, the Integration 406.3 level, is the analog state ofmaterial embodiment of wholes in relative motion, each an Event 301.2and altogether All Events 201.6, comprising the entire complement ofsingular things and their organized aggregations of parts, pieces, andproperties, which are represented as Event Objects 201.1.3, and theirdescriptive Event Information 202.1.2. The original relation of eventobject and event information is established when owners make claims thatdefine the identity of each thing with symbols—name and unique EventIdentities 201.1.1. FIG. 4 depicts seven universal dimensions ofembodiment in Layers of Objects 201.1;

-   -   201.1.1 Event Identities    -   201.1.2 Event Information    -   201.1.3 Event Objects    -   201.6 Events    -   201.1.4 Event System Objects    -   201.1.5 Event Domain Objects    -   201.1.6 Object of Everything

Each thing in both physical and abstract dimensions is an Event 301.2 inAll Events 201.6. Event forms represented in Model of Everything 1000include embodiments that range from physical to abstract. At this secondstage of deconstruction, the dimensional version of the model includeseverything.

FIG. 5 Extent of Everything

By considering the dimensions of everything, the extent of everythingmay be circumscribed as scope elements shown in FIG. 5. Scope ofEverything 201, which consolidates dimensional terms into one set of sixdimensioned levels of reality which collectively represent everything asinclusive ranges of conceptual description.

-   -   201.1 All Identities    -   201.2 All Information    -   201.3 All Objects    -   201.4 All Systems    -   201.5 All Domains    -   201.6 All Events

In other words, every individual thing known to man could be listed asan identity, as information, as object, as system, as domain, or asevent. And correlatively, there is no thing known to man or that will beknown that doesn't fit under at least one of these umbrella terms. Thus,the scope of the present invention is Unitary Scope 201, all inclusiveof everything, and at this stage of deconstruction, the subjectiveversion of the model includes everything.

FIG. 6 Description of Everything

Scope of Everything 201 labels may be further correlated withsocio-political-cultural dimension as conceptual infrastructure terms asarticulated in FIG. 6. The institutions of everything are:

-   -   Information Reference Architecture 200.1: encompasses principles        of information structure, organization, definition of identities        and constituents.    -   Civil Infrastructure 200.2: encompasses principles of democracy,        self-representation, ownership, rules, values, norms, principles        and processes of citizenship, including original instantiation        and current authentication.    -   Information Infrastructure 200.3: encompasses language,        classification, representation, media, devices, hardware and        software.    -   Physical Infrastructure 200.4: encompasses all people, property,        events, places, ideas, artifacts, objects, assertions;        everything.    -   Process Infrastructure 200.5: encompasses natural systems,        man-made systems, business methodologies, programmatic        structures, functions, and tools, production systems, delivery        systems, supply chain networks, media, devices, hardware and        software.    -   Economic Infrastructure 200.6: encompasses principles of        economics, exchange systems, metrics, markets, financials,        communication, systems, the Internet, the telephone system,        media, devices, hardware and software.

Infrastructure 200 components are inclusive of abstract principles andconventions that people around the world use to define semantic systems,to communicate with one another, to make and use things, and toparticipate in both the community and marketplace. Through multipleversions that articulate and circumscribe deeper and wider definitions,the model continues to apply to and include everything.

FIG. 7 Unitary Reference Architecture Components

FIG. 7 depicts the high-level components of Model of Everything 1000with Unitary Reference Architecture 100, which constitute a copy,pattern, image to be made, miniature representation, and mathematicaldescription of analog |EVERYTHING| including all events 201.6, all eventdomains 201.5, all event systems 201.4, all event objects 201.3, allevent information 201.2, and event identities 201.1. The components thatmake up Unitary Reference Architecture 100 are;

-   -   UR-URL Identifier Method 101    -   List of Everything 102    -   Table of Everything 103    -   Database of Everything 104    -   Platform for Everything 105    -   Web Portal to Everything 106        FIG. 8 Alignment of Scope and Components

FIG. 8 shows the alignment between Model of Everything 1000 componentsand Scope of Everything 201 elements derived according to Levels ofAbstraction 202.2 and Layers of Objects 202.1. Everything in Scope ofEverything 201 is modeled in Model of Everything 1000.

FIG. 9 Relation of Scope and Components

FIG. 9 shows Scope of Everything 201 elements from top to bottom goinginto Model of Everything 1000, which is constructed from bottom to top,built on Unitary Reference Architecture 100. Unitary Infrastructure 200components are the underlying structural members that support theoverall architecture of everything. Dimensions are “rebar” that keepcolumns of part numbers in straight order within states. Scopes are“cross-beams” that span and connect columns to cohere components andparts across the continuum of states.

FIG. 10 Everything Components

Model of Everything 1000 components are modeled after and representcomponents and dimensions of everything. Model of Everything 1000 ismade up of Unitary Reference Architecture 100, Unitary Infrastructure200, Unitary Ontology Architecture 300, Unitary Resource DescriptionFramework 400, Unitary Process 500, and Unitary Apparatus 600.

FIG. 11 Unitary Reference Architecture Components

Unitary Reference Architecture (URA) 100 is made up of UR-URL IdentifierMethod 101, List of Everything 102, Table of Everything 103, Database ofEverything 104, Platform for Everything 105, and Web Portal toEverything 105.

FIG. 12 UR-URL Identifier Method Components

UR-URL Identifier Method 101, also referred to as Unitary IdentityArchitecture and Unitary Identity, is made up of UR-URL 101.1, Name101.2, Owner 101.3, Authority 101.4, Keywords 101.5, and Path 101.6.

UR-URL 101.1 is made up of unique relative referential geotemporalincept coordinates XYZT/GT asserted by makers. Correlated terms includebut are not limited to: UR-URL Real Identifier 101.1.1, XYZT/GT Incept101.1.2, XYZT/GT Now 101.1.3, XYZT/GT Extension 101.1.4, Other Extension101.1.5, Other Address 101.1.6, and Other ID 101.1.7.

UR-URL 101.1 establishes a direct association by owner-maker betweenreal identity and real identifiers coincident with event time andlocation. The form of address a particular event takes, be it coordinateor postal or other, is immaterial to the fact of specificity of adistinct location in spacetime that may be converted to numerousequivalent formats. What makes the identifier work universally foreverything and everyone everywhere in all time isn't simply location, asin common navigation systems, and it isn't simply time, as in commondate/time stamping, and it isn't simply the combination of location anddate/time. What makes UR-URL 101.1 work universally is the combinationof location/date/time with assertion of incept identity ownership in asystem of legally authenticated claims—exactly what the public domain isin analog. We could not have democracy if vendors owned citizens' legalidentities, yet we continue to evolve the Internet—a system ofartificial identities—as though it could and will be a substitute forreal analog establishments and institutions. It can't. The presentinvention can.

Point of clarification: UR-URL will work as an identifier for everythinganytime anywhere in any given system, even without the principle ofincept ownership or other components of Unitary Reference Architecture100. But the only way to make one universal system of |EVERYTHING| iswith Unitary Reference Architecture which employs universal principlesof private ownership and citizenship used by people and governmentsaround the world. Officially authenticated privately controlled eventidentity ownership is the key to utility as one universal system ofinformation addresses in one Model of Everything 1000.

Furthermore, any prior art identifier method may be used modularly withUnitary Reference Architecture 100 components—List, Table, Database,Platform, Web Portal, Ontology, RDF—in place of UR-URLs to build a“Model of Something”. However, the resultant model can represent only aportion of |EVERYTHING| insofar as prior art identifier methods arefinite combinations and can only identify as many things in |EVERYTHING|as code structure permits.

Name 101.2 is made up of alpha-numeric characters and/or symbols asasserted by makers. Correlated terms include but are not limited to:Claimed Identity Name 101.2.1, Real

Name 101.2.2, Real Identity 101.2.3, Named Identity 101.2.4, Title101.2.5, Term 101.2.6, Other Designation 101.2.7.

Owner 101.3 is made up of the legal name of the entity asserting a claimto ownership of person, property, or idea. Correlated terms include butare not limited to: Claim Maker Owner 101.3.1, Functional Owner 101.3.2,Maker 101.3.3, Inventor 101.3.4, Discoverer 101.3.5, Parent 101.3.6, andLegal Agent 101.3.7.

Authority 101.4 is made up of the legal name of the entity or instrumentcorroborating or authorizing the claim and instantiating the entity,i.e. Department of Vital Statistics authenticates and records birthsinstantiating person entities as citizens; contract documents authorizeexpenditure of enterprise resources and instantiate productionprocesses. Correlated terms include but are not limited to: OfficialIncept Authentication 101.4.1, Official Authentication 101.4.2, OfficialAnytime Authentication 101.4.3, Maker Affidavit Authentication 101.4.4,Witness Affidavit Authentication 101.4.5, Other Legal Authentication101.4.6. The vital step of official authentication is missing in thecurrent embodiment and prior art embodiments with vendor authentication.

Keywords 101.5 is made up of links to related things and ideas. Keywords101.5 can be anything, including but not limited to specific individualterms concatenated in UR-URL 101.1's XYZT/GT method: Coordinate Values101.5.1, Point of Origin 101.5.2, Differential Quantity 101.5.3,Latitude 101.5.4, Longitude 101.5.5, Elevation 101.5.6, Time 101.5.7, GT101.5.8, Other Legal Designation 101.5.9.

Path 101.6 is made up of links to the system or parent that hasconventions, protocols, and references that govern the thing or idea.The path for an information resource might be the owner's website. Thepath for a work center resource might be to its parent department. At aminimum, terms of reference must be specified. Correlated terms thatclarify address nomenclature include but are not limited to: ReferentialSystem 106.1, Parent System 106.2, GPS 106.3, Geo.Domain 106.4, USGS106.5, Metes and Bounds 106.6, Others 106.7.

II List of Everything View—One Dimension

FIG. 13 List of Everything Components

List of Everything 102 is made up of UR-URL 101, Tabular ArchitectureRows and Columns 600.11, and Infinite Range With Infinite UR-URLIdentifier Method Scope 600.13.

FIG. 14 List View

FIG. 14 illustrates a common list form apparatus with TabularArchitecture Rows and Columns 600.11.

FIG. 15 List with Prior Art Reference Architecture

FIG. 15 illustrates a common list form with prior art referencearchitecture comprising an ID Number 101.1.7 which is not infinitelyextensible and which does not apply to everything, depicted as FiniteRange With Finite Identifier Scope 600.16. Every element within a systemmust have a unique identifier. Size of system is limited by availablecombinations generated by the identifier method's code syntax. GUID has41 characters which yields over 3E+49, or,33,452,526,613,163,800,000,000,000,000,000,000,000,000,000,000,000unique identifiers. That looks like a lot of identifiers, but it's stilla finite number and not remotely enough for everything.

FIG. 16 List with Unitary Reference Architecture

FIG. 16 illustrates List of Everything 102, and contrasts prior artidentifier methods' finite range depicted in FIG. 15 with UR-URLIdentifier Method 101 and its Infinite Range With Infinite UR-URLIdentifier Method 600.13. This is a fundamental distinction between thepresent invention and prior art lists: the capacity to enumerateeverything.

List of Everything 102 is the most elementary expression of everythingin apparatus, consisting of one infinitely extensible column containingjust UR-URL 101.1 identifiers which define a field in “spacetime” andrelate point addresses with Event Potential 302.7 identity. An exampleis List of Everything 102 with the system identity “navigationinstructions” comprising a single column of executable identifiers whereboth locations within the defined field—where the object of theinstructions is scheduled to be and the time it's supposed to bethere—are contained in the object's UR-URL Identifier 101.1. The thing,the place, the time, and sequence of events are simultaneouslyrepresented as “a path” of successive UR-URLs 101.1.

More commonly, List of Everything would contain columns for UR-URLIdentifier 101.1 and Name 101.2, a simple binary pair. In general termsof tabular architecture, each data column represents a property ordimension held in common by all information events recorded in rows. Theunique identifier column is mandatory, and not counted as a dimension.Therefore, List of Everything 102 with sequential UR-URLs 101.1 isapparatus in zero dimension. List of Everything 102 with UR-URL 101.2and Name 101.2 has one dimension—Name 101.2, the identity dimension, andis apparatus in one dimension.

III Table of Everything View—Two Dimensions

FIG. 17 Table of Everything Components

Table of Everything 103 is made up of UR-URL Identifier Method 101, Listof Everything 102, Infinite range With Infinite UR-URL Identifier MethodScope 600.13, Unitary Ontology Architecture 300, Unitary ResourceDescription Framework (RDF) 400, Commercial Off The Shelf (COTS) or OpenSource Computer System 600.1, Tabular Architecture Columns and Rows600.11, COTS or Open Source Spreadsheet Software With Search andHyperlinks 600.5, Variable Columns 600.17, Event Data 600.2. These tenparts are common where Table of Everything 103 is a component.

FIG. 18 Table View

FIG. 17 illustrates a common table form apparatus with TabularArchitecture Rows and Columns 600.11 and Variable Columns 600.17.

FIG. 19 Table with Prior Art Reference Architecture

FIG. 19 illustrates a common table form apparatus with TabularArchitecture Rows and Columns 600.11, Variable Columns 600.17, and priorart reference architecture comprising an ID Number 101.1.7 which is notinfinitely extensible and which does not apply to everything, depictedas Finite Range With Finite Identifier Scope 600.16.

FIG. 20 Table with Unitary Reference Architecture

FIG. 29 illustrates a table with Tabular Architecture Rows and Columns600.11 and Variable Columns 600.17, with Unitary ReferenceArchitecture's UR-URL 101, and contrasts prior art identifier methods'finite range with UR-URL 101 and its Infinite Range With Infinite UR-URLIdentifier Method 600.13. This is a fundamental distinction between thepresent invention and prior art tables: the capacity to enumerateeverything.

FIG. 21 Top-Level Ontology

Things in reality come in wholes and are described in terms of featuresand attributes, which are arranged in systems—systems of systems. Amodel of what exists in a system is called an ontology. The wordtraditionally refers to the study of existence—everything—the nature ofbeing. Simply put, technology-wise, an ontology is the map of “kinds” inthe whole system |ANYTHING|. It stipulates conceptual linkage betweenand across subsystems and components, and shows how everything in scopeis connected and organized. Node/category names represent a particulardimension, nature, or essential property shared by sets within thesystem. Irreducible common denominators are called primitives oruniversal types.

Broadly speaking, ontologies tell the computer how to “know” whatsomething “is” by suggesting associations and patterns between kinds andtypes so “likeness” can be reduced to math, which is the languagecomputers speak. A computer thinks by reading lists really fast. Just asit's easier for people to find a book in the library by using thesubject and author guides, so classification makes computer processingfaster and more efficient. Search engines use this basic principle tomeasure keyword related value equivalence to rank results. On a deeperlevel, ontologies provide a logical basis for relating semantic conceptswith programming rules so software agents can more closely simulatehuman reasoning processes.

Developing an ontology includes₂₉:

-   -   Defining the scope of constituency, what it's an ontology of;    -   Grouping the constituents in classes and subclasses;    -   Ordering the classes and subclasses in a hierarchy of        categories;    -   Defining roles and properties of classes;    -   Specifying values for instances of properties.

When the categories and types are defined, you can create a knowledgebase by listing individual elements and using the classification termsto label, organize, and cross-reference at every level of description.

Popular enterprise programs are based on tables and requests. Requestsare operations performed on a specific dataset drawn from one or moretables. Each row in a human resource database represents a person, akaresource event object. The columns have field category names like jobtitle, departmental assignment, pay grade, skill classification, homeaddress and phone, and each object has specific values in its row foreach of the types of information. Similarly, an inventory controldatabase lists products, equipment, tools, materials, and othercorporate assets along with descriptive fields such as capacity,location, quantity, and cost. Software operations select and manipulatethese various “kinds” of data for display in reports and graphics.

Individual values have particular syntax that matters. If one companyuses the name format “Last, First, Middle” and partners use “FirstMiddle Last” it takes an extra step (and extra cost) to convert one orthe other to match. Agreement up front—first and foremost, on theidentifier method, and second, on the “pick-list” for keyword categoriesand types—facilitates integration. An event ontology standardizes the“kinds” and resource description framework (RDF) simplifies consistentapplication. Unitary Reference Architecture 100, Unitary Ontology 300and Unitary RDF 400 establish a common basis for common purpose.

Object oriented systems and their ontologies start out by dividingeverything into “physical” or “abstract” groupings as the first levelduality of entity condition. Unitary Ontology Architecture 300 clarifiesthe term “abstract” by making explicit in the deeper term “assertion”the fact that ideas, as well as their electronic replicas, are created,discovered, and made “legally real” by human articulation, application,authentication, agreement, and public recording of artifact. In the realworld, there is a significant difference between an original and a copy.

The largest set is not all objects or all entities. It is All Events201.6, unified, integrated, and differentiated. Everything is an Event301.2. Event condition is either Object 301.3 or Assertion 301.4. Anassertion is a claim by a maker about their person, property, principle,or transaction—the four states of event, or, event “embodiments”.Assertions are abstract ideas made concrete through declaration (a claimby one person), contract (a claim made by two or more people), orcollective agreement (a statement of principle; a law, which is eithertheoretical or statutory; or a primitive, an elemental force or singularessence). Transaction is the assertion of performance.

The terms Event 301.2, Object 301.3, and Assertion 301.4 are universal,comprehensive in their plurality and singular in their extremity. Upondeconstruction, each has multiple terms of inference. Event Object 301.3and Event Assertion 301.4 were defined on Page 7 [0025] inclusively assynonymous with generally held top-level divisions of everything, i.e.physical or non-physical, tangible or intangible, matter or mind, thingor concept, object or subject, property or agreement, etc.

Conditional duality is resolved by symmetry in that Event Objects 301.3and Event Assertions 301.4 about object constituents and relations sharethe same identifiers.

Unitary Top-Level Ontology 301.1 is made up of Events 301.2. Events301.2 are made up of Objects 301.3 and Assertions 301.4. Objects areeither Person 301.5 or Property 301.6, and Assertions 301.4 are eitherPrinciple 301.7 or Transaction 301.8. Everything is an Event 301.2, andnothing that exists is not either Person 301.5, Property 301.6,Principle 301.7 or Transaction 301.8. The model continues to apply andextend to everything.

FIG. 22 Event Ontology

Unitary Event Ontology 301 depicted in FIG. 22 is derived using Levelsof Abstraction 201.2 in a process of deconstruction. Unitary EventOntology 301 includes and expands Unitary Top-Level Ontology 301.1. ThePrimitive Entity 300.1 for the whole ontology, what the ontology is asystem “of”, is Event 301.2. An ontology of |EVERYTHING|is necessarilyan event ontology.

The Condition 403.5 of an Event 301.2 is either Object 301.3 orAssertion 301.4. The States 404.5 of Events 301.2—the embodiments—arePerson 301.5, Property 301.6, Principle 301.7, and Transaction 301.8.Classes 407.5 and Sub-Classes 300.2 would fit as nodes under States404.5 in a larger-sized ontology map, but have been presented in tabularform to fit on one page.

Persons 301.5 are either Real 301.9 or Fictitious 301.10. Real Persons301.9 are of age and/or competent to make contracts or not, representedby Sui Juris 301.9.1 and Non-Sui Juris 301.9.2 sub-class primitives.Fictitious Persons 301.10 are legal entities that are not real persons,and are represented by For Profit 301.10.1 and Non-Profit 301.10.2sub-class primitives.

Property 301.6 is Real 301.11, Personal 301.12, Intellectual 301.13, andPublic 301.14. Real Property 301.11 is represented by Land 301.11.1 andRights 301.11.2 sub-class primitives. Personal Property 301.12 isrepresented by Tangible 301.12.1 and Intangible 301.12.2 sub-classprimitives. Intellectual Property 301.13 is represented by Instrument301.13.1 and Information 301.13.2 sub-class primitives. Public Property301.14 is represented by Environment 301.14.1 and Emblem 301.14.2sub-class primitives.

Principle 301.7 is Primitive 301.15, Law 301.16, or Standard 301.17.Primitive 301.15 is represented by Singularity 301.15.1 and Force301.15.2 sub-class primitives. Law 301.16 is represented by Statutory301.16.1 and Theoretical 301.16.2 sub-class primitives. Standard 301.17is represented by Definition 301.17.1 and Convention 301.17.2 sub-classprimitives.

Transaction 301.8 is claim 301.18, Function 301.19, or Action 301.20.Claim 301.18 is represented by Contract 301.18.1 and Declaration301.18.2 sub-class primitives. Function 301.19 is represented byOperation 301.19.1 and Office 301.19.2 sub-class primitives. Action301.20 is represented by Act 301.20.1 and Obligation 301.20.2 sub-classprimitives.

Prior art ontologies' top-level system identity is most often “entity”so the ontology is a system of “entities” and everything within thesystem is an instance of “entity”. The computer world isobject-oriented, based on the principles of information systems.Digitization is an abstraction itself. The computer world begins anentire dimension away from real. In digital terms, an object is anentity and a person is an object. Not so in the real world and not so atthe higher level of Unitary Ontology, which is based on the highercombination of the principles of information systems and the principlesof private ownership and citizenship and the principles of relativity.

The present invention must necessarily begin at the higher level,“event”. Everything is really an event. Everything is not really anentity. By moving up a level of abstraction, Unitary Ontology 301 comesinto the real world and provides superordinate primitive terms for thereal-world dimension of formal instantiation of entity that is integralto real identity—to citizenship, participation in the economy,self-representation.

In the real world, a baby is not a citizen—not a real entity with legalstatus—until incept (birth) is claimed by makers (parents),authenticated by witness (usually the hospital) and officially recordedin the public rolls. In the top-levels of description of everything, theterms “condition” and “state” and “class” correspond to legaldefinitions of rights and responsibilities. This vital firstinstantiation step in the information life-cycle of the real world ismissing in object ontologies and in prior art identification anddescription schemas. Unitary Event Ontology 301 is an ontology ofeverything in the real world and in the information world.

FIG. 23 Relative Event Ontology

The Statement of Principle 302.8 and design specification for awhole-system information model are derived from the following excerptfrom Einstein's Theory of Relativity₂₄:

-   -   “Every description of the scene of an event or of the position        of an object in space is based on the specification of the point        on a rigid body (body of reference) with which that event or        object coincides. This applies not only to scientific        description, but also to everyday life.”        The present invention interprets this statement to mean every        event description has six basic elements:    -   1. Point 302.2 (the actual thing, or entity that “has” the        objects in relation);    -   2. Reference-Body 302.6 (the standard, or “known” point of        origin to measure “from,” the governing constraints);    -   3. Observer 302.3 (everything is relative to the observer);    -   4. Position 302.1 (the mathematical coordinates of the point's        location relative to the reference body);    -   5. Scene 302.5 (objects and assertions about object constituents        and relations);    -   6. Specification 302.4 (explicit or detailed statement of legal        particulars).

These groupings are herein considered primitives, or elementary classesin an ontological framework. Things and ideas—entities, objects andartifacts, real and virtual, animate and inanimate—have all six eventelements; Scene 302.5 is all inclusive of event constituents 405,resources 407, and relations 408.

Event Potential 302.7 represents that state of being between conceptionand actualization, and all that exists are points withoutdescription—available UR-URL 101.1 identity-identifier-addresses withoutobjects. In order for UR-URL 101.1 or any identifiers to be associatedwith points/objects, there have to be the other four elements. There hasto be a position, which is a coordinate differential in three vectordimensions—latitude, longitude, and elevation plus time; there has to bea reference-body to measure the coordinates “from”; there has to be anentity doing the measuring and naming; and the measurer-namer has to“specify” details of event properties.

Fewer than six terms may be used to describe |EVERYTHING| where two ormore terms are identical, such as in a private system where owner,authority, and user are one and the same entity, and in cases where itis not necessary to repeat parameters set at the system level, such aspath where all objects in a system share the same path.

Relative Ontology 302 depicts the universal generic structure of anevent system. Relative Ontology 302 terms circumscribe the entire rangeof “kinds” of information all event objects and all event systems arecomprised “of” and forms the principled premise for Unitary ResourceDescription Framework 400.

FIG. 24 Entity Ontology

Top-Level Ontology 303, detailed in John F. Sowa's 2000 book, “KnowledgeRepresentation,”₃₀ defines categories, subcategories, types, andsubtypes for entity objects and processes in a hierarchical constructwith no redundancy. Category names are designed to be used as uniquetype labels in predicate calculus and are “[ . . . ] defined in terms ofthe role and the relation Has.”₃₀ This is machine-readable logic builtinto the words. The specification is available for download and theintent is for businesses to use these labels for classifying informationassets. When they do, everything will match from the inside out. EntityOntology 303 primitive terms are:

-   -   303.1 Term.Entity ( )=T.    -   303.2 Term._(T)( ).    -   303.3 Term.Independent (I).    -   303.4 Term.Relative (R).    -   303.5 Term.Mediating (M).    -   303.6 Term.Physical (P).    -   303.7 Term.Abstract (A).    -   303.8 Term.Actuality (IP)=Independent∩Physical.    -   303.9 Term.Form (IA)=Abstract∩Independent.    -   303.10 Term.Prehension    -   303.11 Term.Proposition (RA).    -   303.12 Term.Nexus (MP)=Physical∩Mediating.    -   303.13 Term.Intention (MA)=Abstract∩Mediating.    -   303.14 Term.Continuant (C).    -   303.15 Term.Occurrent (O).    -   303.16 Term.Object (IPC)=Actuality∩Continuant.    -   303.17 Term.Process (IPO)=Actuality∩Occurrent.    -   303.18 Term.Schema (IAC)=Form∩Continuant.    -   303.19 Term.Script (IAO)=Fomm∩Occurrent.    -   303.20 Term.Juncture (RPC)=Prehension∩Continuant.    -   303.21 Term.Participation (RPO)=Prehension∩Occurrent.    -   303.22 Term.Description (RAC)=Proposition∩Continuant.    -   303.23 Term.History (RAO)=Proposition∩Occurrent.    -   303.24 Term.Structure (MPC)=Nexus∩Continuant.    -   303.25 Term.Situation (MPO)=Nexus∩Occurrent.    -   303.26 Term.Reason (MAC)=Intention∩Continuant.    -   303.27 Term.Purpose (MAO)=Intention∩Occurrent    -   303.28 Term.Absurdity (IRMPACO)=⊥.    -   303.29 Term.Intermediate Category    -   303.30 Central Category        FIG. 25 Object Ontology

The IEEE₃₁ Suggested Upper Merged Ontology (SUMO) 304, a proposed openstandard ontological framework and the collaborative result of some ofthe best thinkers in the Internet world, is shown in part in FIG. 25. Itis linked to Sowa's Top-Level Ontology 303, subordinate in position, andpicks up with object ontology where Sowa's entity ontology leaves off.

Sevcenko's₃₂ free online SUMO Browser 304 offers SUMO Term Search 304.1and displays derivative concepts in easy-to-read tree diagrams shown asSUMO Search Results 304.2, permitting quick selection of lowest commonterms. All the average everyday person needs to know is where to findthem. Additionally, John Sowa's website₃₀ has extensive documentationabout concepts, design principles, and, particularly helpful, detailedexplanations of the math. Copies of relevant portions are included withcited reference volumes.

It would be impossible herein to do justice to Sowa's sophisticated andelegant approach to knowledge representation, and if what you want isinteroperability, this system has widespread support. Custom codes canbe incorporated and it's built for expansion, extensible to any level ofdetail, metatag and beyond. However, any and all categories and typescan be “had” in a Model of Everything 1000. The intent of Unitary EventOntology 301 is to stipulate an all-inclusive instantiating constructwithin which any number of classification systems may be usefullyemployed—i.e. OWL and other domain ontologies may also be optionallyselected in users' keyword claims, but not for instatement terms.Unitary Event Ontology 301 provides primitive designations forlegitimizing condition, class, state, and form. For categories andtypes, the Sowa Top-Level Ontology 303 and IEEE Suggested Upper MergedOntology 304 represent industry best practices and provide primitivecategory labels for entities and objects, both physical and abstract,from planets to quantum theory.

FIG. 26 Ontology of Origination

Unitary Ontology Architecture 300 must extend to all aspects anddimensions of being or it wouldn't be |EVERYTHING|. This necessitatesincorporating provision for belief systems, which are entered asassertions by makers. Ontology of Being 305 shows Eddy's construct₃₃,Infinite Mind and Its Infinite Manifestation, represented by synonymousprimitives: Principle 305.1, Mind 305.2, Soul 305.3, Spirit 305.4, Life305.5, Truth 305.6, Love 305.7, and further described as All Knowing305.8, All Acting 305.9, All Seeing 305.10, All Being 305.11, All Wise305.12, All Loving 305.13, Eternal 305.14, All Substance 305.15,Intelligence 306.16. These terms represent the constituents andrelations of being. Ontology of Being 305 provides neutral and flexibleprimitive classification labels that bridge the space between seen andunseen, what we can touch and what we believe.

FIG. 27 Ontology of Dimension

Young's construct₃₄, Ontology of Dimension—Four Levels of Reality 306,divides everything into four dimensions: I. Purpose 306.1, II. Value306.2, III. Concept 306.3, and IV. Matter 306.4.

FIG. 28 Ontological Integration

The composite in FIG. 37, Integrated Ontology 307, aligns primitivesections from four separate sources. Alone, each depicts the author'scomplete view of everything in reality. The superordinate levelinclusively represents the nature of being and progress as defined byEddy 305. Unitary Identity Architecture 101 precedes Relative Ontology302 illustrated in the next section, and Unitary Event Ontology 301 inthe middle. The next latticework is a rendering of the Sowa Top-LevelOntology 303 for all-purpose object entity description. SUMO 306 andexpanding derivatives are referenced but not shown. Sowa/SUMO aretogether considered one ontology. Each node has a word that signifies anextensible high-order category/type/subtype.

In addition to establishing legitimacy corresponding to analoginstantiation, artifacts, and instruments, the further purpose ofUnitary Event Ontology 301 is to provide evidence that the domain|EVERYTHING|, as defined herein, and claimed by the present invention,is indeed inclusive and extends to everything known. No other methodclaims all events, which if you agree with Einstein, is everything. Noother method claims all objects and all assertions, which is everythingif you use common non-relativistic definitions. Together, these fourunique and complementary ontologies comprise an all-encompassing set ofgeneral summary-level category codes/labels for our many diverse claimsand agreements about individual and collective human experience.

The components of Integrated Ontology 307 are Ontology of Being 305,Relative Ontology 302, Unitary Event Ontology 301, Entity Ontology 303,Object Ontology 304, and Unitary Reference Architecture 100.

FIG. 29 Dimensional Integration

Young's Ontology of Dimension 306 is overlaid Integrated Ontology 307 tocreate Dimensioned Integrated Ontology 308. There is alignment betweenconstructs, which indicates model coherence at fundamental levels.

FIG. 30 Alignment Between Primitive Terms

The present invention, Model of Everything With UR-URL Identity,Identifier, Addressing, and Indexing Method, Means, and Apparatus, canidentify, address, index and integrate in an information table everymolecular constituent of every cell of every person, place, and thing onthe planet. The present invention can also include every idea everclaimed by anyone in all time. In terms of detail, how much is enoughand how much is too much?

Enough is a function of purpose. Too much has consequences for privacy.The burning question today, in terms of the Internet and web service,is, “What kinds of information are needed to describe things well enoughfor discovery?” “Well enough” depends on who's looking and what's beingdescribed. Business needs to align transaction data formats for supplychain partnership automation. When it's business being described, “well”is a matter of common interest in specific fields and codes. But whenit's people, “enough” more often than not means nothing at all. We'djust as soon nobody knew anything about us. The fact of the matterremains, the end product of industry efforts to standardize the “kinds”of information they exchange will be a set of basic templates thatspecify how information about private citizens is collected and used.The kinds matter a lot.

Privacy isn't about “trust providers” protecting private information;it's about their not owning and controlling it in the first place. Weshould be asking, “What are the critical kinds of information we wantvendors to share with each other about us and our property?” The kindshave both legal and personal ramifications. For this reason, and becausequantity doesn't mean quality, just higher cost and longer wait times,Unitary Technology reframes the inquiry to, “How little is adequate?”

All information winds up in tables with columns and rows, so the answerboils down to the labels that should be in the columns—labels that, inorder to be universal, have to apply to and describe each thing in|EVERYTHING| in sufficient detail so as to differentiate it fromeverything else. “Resource Description Framework” refers to theparticular selection of terms as column labels in the TabularArchitecture Rows and Columns 600.11 “columns”.

Alignment between standard primitive ontological constructs in ResourceDescription Synthesis 409 suggests common column label RDF requirementsfor event description and discovery. Relative Ontology's 302 sixcomponents map to our analog 413 minimum terms for valid contract, thenorm for authenticating identity of person and property. There iscommonality with John F. Sowa's Top-Level Categories 303, and there's aparallel with standard programming n-tuple logic 411. In aggregation,they point to six basic ingredients in all event objects—URA Terms 101.

Relative Ontology 302 primitives are: Position 302.1, Point 302.2,Observer 302.3, Specification 302.4, Scene 302.5, and Reference-Body302.6. Analog primitives are Address, Name, Maker(s), Contract/Artifact,Claim(s), and Witness 101.4.5. Sowa primitives are Proposition 303.11Actuality 303.8, Prehension 303.10, Intention 303.13, Nexus 303.12, andForm 303.9. Logic 411 primitives are ID 101.1.7, Bearer 411.1, NormativeAgent 411.2, Condition of Obligation 411.3, Obligation 411.4, andSanction 411.5. ERP 412 primitives are ID 101.1.7, Name 101.2,Functional Owner 101.3.2, Work Order/Statement of Work 412.1, Resources405 and Relations 408, and System 406.

Considered in concert, like terms from the several ontologies aresynthesized conceptually in Unitary Resource Description RDF Array 400:Identifier 401, Identity 402, Origin 403, Agreement 404, Constituents405, and System 406. Then, RDF Array 400 terms are reduced to simplestcommon user-friendly Unitary Reference Architecture's UR-URL IdentifierMethod 101 terms: UR-URL 101.1, Name 101.2, Owner 101.3, Authority101.4,. Keyword 101.5, and Path 101.6.

The answer to the question, what kinds of information are needed todescribe things well enough for discovery, is, not much—six things, asindicated by Relative Ontology 302 and transformed to common termsUnitary RDF 400 in Resource Description Synthesis 409. However,subdividing constituent into keyword, profile, and activity more closelymatches enterprise planning.

The sum total of enterprise assets is a semantic list ofresources—things. The objective of business is to leverage human capitalassets with intellectual property assets in combination with real andpersonal property assets following policy, procedure, and process assetsto make other things that are worth more in combination than alone.

Business has resources 407. Business has activity 408.1. Activity 408.1is the assertion of relation between resources. Activity 408.1 is anevent 301.2 and a system 406 and an object 301.5 with incept andconstituents relating. Just another line item in an enterprise model ofModel of Everything 1000. Resources 407 are resources 407, regardless ofstate 404.5. They all have the same basic kinds of descriptive elements.Differences are all situational. That is, event conditions differ, butwhen all's said and done, each thing is a system and is in a system. Allevent objects 201.1.3 and event systems 201.1.4 share six commonprimitive terms.

Keyword 101.5 is a more common term than Constituent 405, and can referto anything, including Profile 407 and Activity 408.1. They can all bein the same column, but it's useful to see three groupings. Whatbusiness needs is a list of resources with common RDF in a table thatcan be queried—an enterprise Table of Everything 103.

FIG. 31 Matrix of Ontological Terms

Synthesis of ontological constructs produced RDF Array 400, which isfurther considered in Resource Description Matrix 410, where the termsof Unitary Resource Description Framework 400 are arrayed in fivecross-sections that bring out particular facets of application ashigh-order ontological primitive labels for the many dimensions of|EVERYTHING|: Expression 400.5, Aspect 400.4, Purpose 400.3, Set 400.2,and Logic: Has 400.1.

-   -   The Expressions 400.5 of Unitary RDF 400 are:        -   Address 401.5, Element 402.5, Condition 403.5, State 404.5,            Category 405.5, Domain 406.5, Class 407.5, Union 408.5.    -   The Aspects 400.4 of Unitary RDF 400 are:        -   Uniqueness 401.4, Representation 402.4, Inception 403.4,            Legitimacy 404.4, Composition 405.4, Orientation 406.4,            Eligibility 407.4, Context 408.4.    -   The Purposes 400.3 of Unitary RDF 400 are:        -   Differentiation 401.3, Designation 402.3, Ownership 403.3,            Instantiation 404.3, Classification 405.3, Integration            406.3, Utilization 407.3, Operation 408.3.    -   The Sets 400.2 of Unitary RDF 400 are:        -   Record 401.2, Register 402.2, Ontology 403.2, Concordance            404.2, Taxonomy 405.2, Architecture 406.2, Pool 407.2, Model            408.2.    -   The Logic: Has 400.1 with Unitary RDF 400:        -   Has UR-URL 401.1, Has Name 402.1, Has Owner 403.1, Has            Authority 404.1, Has Keyword 405.1, Has Path 406.1, Has            Profile 407.1, Has Activity 408.1.            FIG. 32 Ontology of Everything

Unitary Integrated Ontology 309 arrays Unitary RDF 400 terms andExpressions 400.5 against the combined components of Integrated Ontology307 to illustrate top-to-bottom applicability from the highest orderabstract concepts and event incept origination and instantiation all theway through entity categories to object forms, both physical andabstract. There is a primitive for everything and no thing exists thathas no primitive. Unitary Integrated Ontology 309 is an ontology of|EVERYTHING| and demonstrates universal inclusion.

Asterisks note supplementary headers that align with titles and addsymmetry and coherence to the illustration. Every effort was made toensure no terms overlap between ontologies, and that unitary termscorrespond with commonly accepted legal definitions. The intent anddesign of Unitary Ontology Architecture 300 is that the final constructhave no redundancy, and as depicted herein, labels are unique across theontologies integrated.

FIG. 33 Table with Unitary Resource Description Framework (RDF)

FIG. 33 illustrates a table with Tabular Architecture Rows and Columns600.11, Variable Columns 600.17, Infinite Range With Infinite UR-URLIdentifier Method 600.13, and List of Everything 102, with UnitaryResource Description Framework 400 in six terms of UR-URL IdentifierMethod 101: UR-URL 101.1, Name 101.2, Owner 101.3, Authority 101.4,Keyword 101.5, and Path 101.6, as might be used in a public domaincontext.

FIG. 34 Table with Extended Unitary Resource Description Framework (RDF)

FIG. 34 illustrates a table with Tabular Architecture Rows and Columns600.11, Variable Columns 600.17, Infinite Range With Infinite UR-URLIdentifier Method 600.13, List of Everything 102, with extended UnitaryResource Description Framework 400 in eight terms of UR-URL IdentifierMethod 101: UR-URL 101.1, Name 101.2, Owner 101.3, Authority 101.4,Keyword 101.5, Path 101.6, Profile 101.7, and Activity 101.8, as mightbe used in an enterprise context.

FIG. 35 Table with Simple Unitary Resource Description Framework (RDF)

FIG. 35 illustrates a table with Tabular Architecture Rows and Columns600.11, Variable Columns 600.17, Infinite Range With Infinite UR-URLIdentifier Method 600.13, and List of Everything 102, with SimpleUnitary Resource Description Framework 400 in four terms of UR-URLIdentifier Method 101: Name 101.2, Keyword 101.5, and Path 101.6, asmight be used in a private context where owner and authority are one andthe same as the user and it is not necessary to duplicate entries.

FIG. 36 Table with Unitary Reference Architecture, Ontology, (RDF),Hardware and Software

FIG. 36 illustrates Table of Everything 103 with Tabular ArchitectureRows and Columns 600.11, Variable Columns 600.17, Infinite Range WithInfinite UR-URL Identifier Method Scope 600.13, List of Everything 102,Unitary Ontology Architecture 300, Unitary Resource DescriptionFramework 400, UR-URL Identifier Method 101, COTS or Open SourceComputer System 600.1, COTS or Open Source Spreadsheet Software WithSearch and Hyperlinks 600.5, and Event Data 600.2, altogether comprisingTable of Everything 103. Table of Everything 103 is apparatus intwo-dimensions.

While Model of Everything 1000 may be constructed using old-fashionedanalog media, the addition of COTS or Open Source Spreadsheet SoftwareWith Search and Hyperlinks 600.5 expands the utility of Table ofEverything 103. The following definitions of the term “table” explainadditional functionality:

-   -   Tables as features offered by application programs₂₈        -   Traditionally, the most familiar media for creating and            storing tables have been pen and paper. Given the            proliferation of computers at home and in the workplace,            computer representations of “paper tables” have become            widespread. Common software applications give users the            possibility of generating, manipulating, and editing both            table data and table formats with ease. Such applications            include: word processing applications; Desktop publishing            software; spreadsheet applications; presentation software;            and        -   tables specified in HTML or another markup language.    -   Tables as techniques used in programming computers₂₈        -   Data tables are used extensively in computers, in forms as            diverse as equal-sized and consecutive blocks of memory            locations, on one hand, and “scatter-storage” schemes            relying on what are more conventionally known as hash            functions, on another. Each is a distinct data structure in            computer science.    -   Spreadsheet₂₈    -   A spreadsheet is a rectangular table (or grid) of information        -   Table of Everything 103 may be created in common commercial            spreadsheet programs such as Excel and Lotus 1-2-3. Each row            of Table of Everything 103 contains a record for one thing,            and columns contain terms for each thing according to the            column labels. Terms are also “things” with their own            records, which are connected by hyperlink. Thus, every term            in every column represents either a value or a link to that            term's identity record in Table of Everything 103.            IV Database of Everything View 3            FIG. 37 Database of Everything Components

The components of Database of Everything 104 are: UR-URL Identifiermethod 101, Table of Everything 103, Variable Relational Tables 600.15,COTS or Open Source Computer System 600.1, COTS or Open Source DatabaseSoftware 600.6, Infinite Integration With UR-URL Identifier Method Scope600.12. Database of Everything 104 contains Table of Everything 103, butindividual Table of Everything 103 parts included are not calledindividually.

FIG. 38 Database View

FIG. 38 illustrates a common database form apparatus with TabularArchitecture Rows and Columns 600.11, Variable Columns 600.17, andVariable Relational Tables 600.15.

FIG. 39 Database with Prior Art Reference Architecture

FIG. 39 illustrates a common database form apparatus with TabularArchitecture Rows and Columns 600.11, Variable Columns 600.17, VariableRelational Tables 600.15, with prior art reference architecturecomprising an ID Number 101.1.7 which is not infinitely extensible andwhich does not apply to everything, depicted as Finite Range With FiniteIdentifier Scope 600.16, and which is not infinitely integrateable,depicted as Finite Integration With Finite Identifier Scope 600.14.

FIG. 40 Database with Unitary Reference Architecture

FIG. 40 illustrates a common database form apparatus with List ofEverything 102, Table of Everything 103, Unitary Ontology Architecture300, Unitary RDF 400, Tabular Architecture Rows and Columns 600.11,Variable Columns 600.17, Variable Relational Tables 600.15, with UnitaryReference Architecture's UR-URL 101, and contrasts prior art identifiermethods' finite range with UR-URL 101 and its Infinite Range WithInfinite UR-URL Identifier Method 600.13 and Infinite Integration WithUR-URL Identifier Method 600.12. This is a fundamental distinctionbetween the present invention and prior art databases: the capacity toenumerate everything. A database with Unitary Reference Architecture 100is a Database of Everything 104.

FIG. 41 Database with Unitary Reference Architecture, Hardware andSoftware

FIG. 41 illustrates Database of Everything 104 components depicted inFIG. 40 with the addition of COTS or Open Source Computer System 600.1,COTS or Open Source Database Software 600.6, and Event Data 600.2.Spreadsheet Software With Search and Hyperlinks 600.5 is also shown andmay be used optionally instead of database software since, as describedin the definitions below, works much the same way.

Row (database)₂₈

In the context of a relational database, a row represents a single,implicitly structured data item in a table. For example, in a table thatrepresents companies, each row would represent a single company; in atable that represents the association of employees with departments,each row would associate one employee with one department.

The implicit structure of a row, and the meaning of the data values in arow, requires that the row be understood as providing a succession ofdata values, one in each column of the table. The row is theninterpreted as a relation variable composed of a set of tuples, witheach tuple consisting of the two items: the name of the relevant columnand the value this row provides for that column.

Each column expects a data value of a particular type. For example, onecolumn might require a unique identifier, another might require textrepresenting a person's name, another might require an integerrepresenting hourly pay in cents.

Column (database)₂₈

In the context of a relational database, a column of a table is a set ofdata values of a particular simple type, one for each row of the table.The columns provide the structure according to which the rows arecomposed. For example, a table that represents companies might have thefollowing columns: ID (integer identifier, unique to each row); Name(text); Address line 1 (text); Address line 2 (text); City (integeridentifier, drawn from a separate table of cities, from which any stateor country information would be drawn); Postal code (text); Industry(integer identifier, drawn from a separate table of industries); etc.

Each row would provide a data value for each column and would then beunderstood as a single structured data value, in this case representinga company. More formally, each row can be interpreted as a relativevariable, composed of a set of tuples, with each tuple consisting of thetwo items: the name of the relevant column and the value this rowprovides for that column.

Database of Everything 104 is an apparatus with tabular architecturecontaining rows of object identity records with corresponding columns ofuniversal Unitary RDF 400 data fields containing terms and valuesspecific to each object and relative to the Unitary RDF 400, andclassified by Unitary Integrated Ontology 309. Terms are also objects inselfsame Database of Everything 104 with original “term object” identityrecords that are also classified with primitive ontological terms drawnfrom Unitary Integrated Ontology 309.

Database of Everything 104 may be created in common commercialspreadsheet and database programs such as Excel, Lotus 1-2-3, dBase, andAccess. These programs have basic tabular architecture 600.11 andfeature search, hotlink, and other programmatic functionality. UnitaryRDF 400 terms in columns represent primitive identities with links toindividual term identity records, thus a Database of Everything 104 in aspreadsheet/database program is a searchable inventory of informationobject identities corresponding to analog objects and assertions in onecross-referenced matrix of everything. Database of Everything 104 isapparatus in three dimensions.

V Platform for Everything View 4

View 4 presents Unitary Process Architecture 500 descriptions, beginningwith examples of programmatic functionality, and concluding with processflow diagrams that illustrate application of Unitary Technology in theoverall socio-political-economic context of access to informationservices and resources in the global electronic marketplace.

FIG. 42 Platform for Everything Components

Components of Platform for Everything 105 are: UR-URL Identifier Method101, Database of Everything 104, Shell 600.4, Unitary Shell 601, COTS orOpen Source Shell Software With Simple Tools 600.7, COTS or Open SourcePredicate Logic Software 600.8.

FIG. 43 Platform View

FIG. 43 illustrates a common shell apparatus 600.4 with several shellsopen. Shells are convenient utility platforms that facilitate simplecode writing with various popular COTS or Open Source scriptinglanguages and object oriented approaches. A shell is a flexible andversatile canvas that when used in tandem with UR-URL Identifier Method101 and Database of Everything 104, along with Computer System 600.1,COTS or Open Source Shell Software With Simple Tools 600.7, and COTS orOpen Source Predicate Logic Software 600.8, becomes a powerfulprogrammatic tool. Terms are defined:

Ontology₃₀

The subject of ontology is the study of the categories of things thatexist or may exist in some domain. The product of such a study, calledan ontology, is a catalog of the types of things that are assumed toexist in a domain of interest D from the perspective of a person whouses a language L for the purpose of talking about D. The types in theontology represent the predicates, word senses, or concept and relationtypes of the language L when used to discuss topics in the domain D. Anuninterpreted logic, such as predicate calculus, conceptual graphs, orKIF, is ontologically neutral. It imposes no constraints on the subjectmatter or the way the subject may be characterized. By itself logic saysnothing about anything, but the combination of logic with an ontologyprovides a language that can express relationships about the entities inthe domain of interest. [Emphasis added.]

N-tuple₂₈

In mathematics, a tuple is a finite sequence of objects (a list of alimited number of objects). (An infinite sequence is a family.) Tuplesare used by mathematicians to describe mathematical objects that consistof certain components.

Usage in computer science₂₈

In computer science (especially in programming languages and databasetheory such as the relational model) a tuple is usually defined as afinite function that maps field names to a certain value. Its purpose isthe same as in mathematics, namely to indicate that a certain entity orobject consists of certain components and/or has certain properties. Inprogramming languages tuples are used to form data structures.

Programming language is defined:₂₈

A programming language or computer language is a standardizedcommunication technique for expressing instructions to a computer. It isa set of syntactic and semantic rules used to define computer programs.A language enables a programmer to precisely specify what data acomputer will act upon, how these data will be stored/transmitted, andprecisely what actions to take under various circumstances.

Spreadsheet programming₂₈

Just as the early programming languages were designed to generatespreadsheet printouts, programming techniques themselves have evolved toprocess tables (=spreadsheets=matrices) of data more efficiently in thecomputer itself. A spreadsheet program is designed to perform generalcomputation tasks using spatial relationships rather than time as theprimary organizing principle. Many programs designed to perform generalcomputation use timing, the ordering of computational steps, as theirprimary way to organize a program.

In a spreadsheet, however, a set of cells is defined, with a spatialrelation to one another. In the earliest spreadsheets, thesearrangements were a simple two-dimensional grid. Over time, the modelhas been expanded to include a third dimension, and in some cases aseries of named grids. The cells are functionally equivalent tovariables in a sequential programming model. References between cellscan take advantage of spatial concepts such as relative position andabsolute position, as well as named locations, to make the spreadsheetformulas easier to understand and manage.

Many of the concepts common to sequential programming models haveanalogues in the spreadsheet world.

Basic₂₈

The idea behind object-oriented programming is that a computer programis composed of a collection of individual units, or objects, as opposedto a traditional view in which a program is little more than a list ofinstructions to the computer. Each object is capable of receivingmessages, processing data, and sending messages to other objects. Inthis way, messages can be handled, as appropriate, by one chunk of codeor by many in a seamless way.

In OOP, objects are simple, self contained and easily identifiable. Thismodularity allows the program parts to correspond to real aspects of theproblem and thereby to model the real world. Object-oriented programmingoften begins from a written statement of the problem situation. Then bya process of inserting objects or variables for nouns, methods for verbsand attributes for adjectives, a good start is made on a framework for aprogram that models, and deals with, that situation.

According to the object-oriented principles, the verb is attached to theobject and logic associated to the requirement is handled in the object.The paradigm of OOP is essentially not that of programming but one ofdesign. A system is designed by defining the objects that will exist inthat system, the code which actually does the work is irrelevant to theobject, or the people using the object, due to encapsulation.

The architecture of Model of Everything 1000 facilitates easy use ofbasic object-oriented programming functionality, and is ideally suitedfor simple predicate logic tools and applications. In addition tointernal cross-referencing by hotlink: 1) links from one object's valueterm to that term's identity object record, 2) links between terms andterms; 3) and links between objects and objects, there is also abuilt-in internal link through Unitary Integrated Ontology to predicatelogic constructions. Logic provides the semantic basis, and UR-URLIdentifiers 101.1 provide the terms inserted into logical forms asrelation variables.

Database of Everything 104, which “goes into” Platform for everything105, is a table with resources in rows and what they “have” in columns.Possession is the relation represented in a system of ownership, i.e.owner has object, object has keywords, resource has role. The symbol ∩means “intersection” or “has.”

Table 2 shows sample “Has Category” fields that might be used in anenterprise information asset management event system database. Eachsuperclass represents a union set [Identifier∩ Set (Code, Value)(Code,Value) . . . ] where codes are class, category, and type labels drawnfrom the ontology and values are object-specific properties andattributes.

TABLE 2 Sample Event Function Set Options (Columns 1-6 and 7-8)IDENTIFIER IDENTITY ORIGIN AGREEMENT CONSTITUENT SYSTEM ∩UR-URL ∩Name∩Owner ∩Authority ∩Keyword ∩Path ∩UR-URL.Extension ∩NameLast ∩OwnerLink∩AuthorityLink ∩Component ∩SysParent ∩InceptLocDateTime ∩NameFirst∩EntityCondition ∩State ∩Feature ∩SysChild ∩NowLocDateTime ∩NameMiddle∩Statement ∩Property ∩SysReference ∩PartNumber ∩Symbol ∩Attribute∩ProductCode ∩Alias ∩Characteristic ∩Identifier ∩Quality ∩Address∩Quantity ∩AddressCode ∩Association ∩Possession ∩Image ∩Graph ID POINTOBSERVER SPECIFICATION SCENE REFERENCE RESOURCE RELATION ∩Profile∩Activity ∩Class ∩Process ∩Form ∩Obligation ∩Office ∩Role ∩Utility∩Relation ∩Capacity ∩Action ∩AccessRule ∩Predicate ∩Performance∩Operation ∩KeyCategory ∩Argument ∩Predecessor ∩Successor ∩Vector∩Function OPTIONAL “SCENE” SPLITS

-   -   Each record has a pair of values in each essential field, and as        many other category/value pairs as desired.    -   Constituent, Resource, and Relation fields can have any        combination of codes and values (or one field “scene” vs.        three).    -   Constraints and relationships are inherited from parent/path.    -   System and code definitions are listed objects with UR-URLs;        codes link to definitions—everything's a link.    -   Objects are entities with constituents, and also constituents        themselves in larger event system objects.    -   An activity is entered as a new event record that “has”        resources in roles—people, property, and processes.    -   Updates are “has” functions that generate event links with new        instances of codes and values for resources used.    -   Each resource has a UR-URL; old identifiers and codes are listed        constituents.    -   Codes may be entered in series [Identifier∩(Code, Value, Value,        Value . . . )].    -   Code pairs too [Identifier∩(Code, Value)(Code, Value)] and        [Identifier∩(UR-URL,UR-URL)(UR-URL,UR-URL)].    -   Shorthand activity programming—use the schedule to embed due        date/time right in planned activity identifiers.    -   Fields may contain any combinations of codes and values.    -   Codes link to code definitions, which are listed resources.    -   Values link to other listed resources or contain literal        strings.

Furthermore, just as programmatic functionality accrues to a spreadsheetwhere “a set of cells is defined with a spatial relation to one another”(per definition of “Spreadsheet Programming”), so UR-URLs are definednot with just spatial relation within the tabular structure of thespreadsheet, but also ontological relation within the Unitary RDF 400structure, and spatio-temporal relation within the UR-URL Identifier's101.1 XYZT/GT structure itself. UR-URLs “are functionally equivalent tovariables in a sequential programming model” and can be used as such.UR-URL Identifiers 101.1 serve as external executable hotlinks that caninvoke identity object terms.

And, abstracting the definition of “programming language” as given,UR-URLs are a programming language. In a modular sub-version Model ofEverything 1000 with the system identity “Software Authoring Program”,everything that software authoring program is “made of”, from thehighest domain groupings to lowest granular object, has a record withfive descriptive terms and UR-URL.

“Programming Language” is just one of the many domains of “SoftwareAuthoring Program” which is in the larger domain “Operating System”.Every term in the whole system has a record and UR-URL. Every“standardized communication technique for expressing instructions to acomputer” has a record and UR-URL. Every “set of syntactic and semanticrules used to define computer programs” has a record and UR-URL.“Programmers can precisely specify what data a computer will act upon”by specifying UR-URLs for the “data”, UR-URLs for the “actions”, UR-URLsfor the “storage and transmission rules”, UR-URLs for conditions thatdefine “circumstances” and alternatives. Architects can also specifyUR-URLs 101.1 for hard-drive addresses, real or referential. UR-URLs101.1 provide an end-to-end architecture for Model of Everything 1000.

Everything means |EVERYTHING| in whatever system is using the presentinvention. A dictionary is a comprehensive listing of original terms(system identity: term definitions) with descriptions, such that, inusage, when a term is specified the description is invoked, which letsus use words as a short-hand for meaning. Model of Everything 1000 is acomprehensive listing of original event records with descriptions thatlet us use UR-URLs as a short-hand for meaning in all kinds of forms,and formats, and sentences, and strings in programming tools that userelation variables.

In Model of everything 1000, the identity-identifier, UR-URL 101.1, isthe platform for universal interoperability.

FIG. 44 Identity Expressions

Event Identity Forms 501 represent simple forms of expression thatassociate UR-URL Identifiers 101.1 with real identity. Makers recordclaims that link entity names with identifiers, as in Unitary IdentityStatement 501.1 and they also record claims that link object names withidentifiers, and object identifiers with object properties, as in 501.2.Multiple assertions may be in one statement, as in Unitary EventIdentity Statement 501.3.

FIG. 45 Logical Expressions

Event Tuple Forms 502 represent simple forms of expression thatassociate subject, object, and predicate, where Tuple Statement 502.1 isa standard construction with prior art identifier and Unitary TupleStatement 502.2 has the same semantic structure with UR-URL Identifiers101.1. A standard N-Tuple Statement 502.3 is likewise compared withUnitary N-Tuple Statement 502.4. UR-URL Identifiers 101.1 may be used torepresent terms in simple COTS or Open Source Predicate Logic Software600.8 logical constructions.

FIG. 46 Correspondence Between Expressions

Event Statement Forms 503 illustrate correspondence between how EnglishLanguage 503.2 terms used in logical constructs to represent thesentence “A cat is on a mat” in examples from Sowa's explanatorymaterial and how UR-URL Identifiers 101.1 terms are used to representthe same sentence “A cat is on a mat.” 503.1 with the same notation andsyntax, substituting UR-URL Identifiers 101.1 for the Event Objects301.3 “cat” and “mat”, and the Event Assertion 301.4 “on”, which wouldcorrelate to identity objects in Model of Everything 1000.

FIG. 47 Description Expressions

Event Description Forms 504 illustrate the use of simple logicalconstructions to enter object identity information in Model ofEverything's 1000 tabular architectures 600.11.

Single Entry 504.1 form associates resource object UR-URL 101.1 withproperties and values entered by makers as Event Data 600.2 or selectedfrom Unitary Integrated Ontology 309, as indicated by the drop selection“Find Term” in both 504.1 and 504.2.

Multiple Entries 504.2 form illustrates how resource object UR-URLs101.1 may be associated with Unitary RDF terms and values in a compoundstatement.

FIG. 48 Programmatic Expressions

Programmatic Forms 505 illustrate three of numerous possible examples ofprogrammatic expressions. Resource Planning 505.1 illustrates a typicalActivity 101.8 Event Object 201.3 as would relate project terms inactivity scheduling programs. The Activity 101.8 is the Event object201.3 that “has” Resources 407, Constituents 405, Relations 408, andValues-Event Data 600.2. Just as Critical Path Method (CPM) Networks areconstructed by associating these elements, so simple logical statementscan associate elements. Elements' UR-URL Identifiers 101.1 could berepresented graphically as a CPM Network Diagram as shown in FIG. 49,CPM 506.2.

Operations Sequencing 505.2 illustrates a typical “object has sequenceof instructions” type of Event Object 201.3, and Binary Pairs 505.3illustrates the simple association of two UR-URL Identifiers 101.1.

FIG. 49 Diagrammatic Expressions

Diagrammatic Forms 506 illustrate four of numerous possible examples ofdiagrammatic expressions that may be represented as logical statementsor graphical elements, depending on what kinds of COTS and Open Sourceand other software programs and objects are employed. Spatialarrangements are facilitated by the relative referential geotemporalcoordinate basis of UR-URL Identifiers 101.1.

Tree 506.1 illustrates a typical hierarchical organization chart typearrangement; CPM 506.2 illustrates a network diagram with UR-URLIdentifiers 101.1 as previously discussed. Cluster 506.3 illustrates ahoney-combed representation of relation and/or sequence of UR-URLIdentifiers 101.1. Map 506.4 represents an object relationship diagramthat maps links between UR-URLs 101.1, such as are used in socialnetwork maps, mind maps, associative diagrams, etc.

FIG. 50 Menu Expressions

Menu Forms 507 is a rendering of a portion of the Microsoft Word filemenu structure. Main menu bars with most frequently used operationsgrouped as sub-menus are common features of software programs ingeneral. Typically, menus are represented as a series of drop-down boxeswith exploding sub-lists of choices, as shown in Prior Art Menus 507.1.

The same menu structure depicted in 507.1 is depicted in Prior Art MenuExpressions 507.2 as would be represented in a logical selectionstatement using UR-URLs, and where, in a Model of Everything 1000 withthe system identity: MS Word, each menu, sub-menu, and code object areline items in the system's model of Database of Everything 104.

FIG. 51 Prior Art Menu Synthesis and Simplification

MS directories are presented in a version of tree form 506.1 turnedsideways that represent paths through the whole. This is a user-friendlyway to present a big-picture view of relationships, and it is anintuitive way to organize information at the architecturallevel—particularly for MS programmers building on the originalconceptual architecture of DOS. Plus, linear structures are well suitedfor computational efficiency.

But in order for trees to maintain relations down through the lowestlevels of granularity, there is redundancy as seen in two instances of“Cancel [X on checkbox] in the third “Drop-Down Sub-Menus” column ofPrior Art Menus 507.1. “Cancel” is an “object” that is repeated manytimes in many of the MS Word menus. Redundancy is also apparent acrossentire complements of “suite” products, as illustrated in Menu Synthesis506.

Menu Synthesis 508 is made up of a table with menu objects grouped byprogram, Twelve Program Objects—One Hundred and Five menu Objects 508.2,and a table with common menu objects each represented just once, OnePlatform—Twenty-Five menu Objects 508.2.

508.1 is made up of a rough tally of menu objects from a twelve-program“premiere” collection of integrated programs that are discussedgenerically but which are based on the MS products used by the inventorto create, illustrate, and specify the present invention. Manycomparable products with similar complements of redundant menu objectsare available through COTS and Open Source sources.

Products shown in 508.1 are also shown in Table 3, and have instances ofmenu types listed. Uncommon menu types are shown in the shaded area.Common suite of products include: Web Browser 508.2.1, Mail Handler508.2.2, Word Processor 508.2.3, Web Page Creation and Editing 508.2.4,Spreadsheet 508.2.5, Database 508.2.6, Graphics 508.2.7, Presentation508.2.8, Publishing 508.2.9, Drawing 508.2.10, Project Management508.2.11, and Directory 508.2.12.

TABLE 3 MS Office Product Main Menu Examples - One Hundred and TwoObjects WEB MAIL WP HTM-ED SS DB GRFX PRES PUB PNT PM DIR File File FileFile File File File File File File File File Edit Edit Edit Edit EditEdit Edit Edit Edit Edit Edit Edit View View View View View View ViewView View View View View Insert Insert Insert Insert Insert InsertInsert Insert Format Format Format Format Format Format Format ToolsTools Tools Tools Tools Tools Tools Tools Tools Tools Tools FavoritesFavorites Table Table Data Effects Slideshow Table Image ProjectFavorites Search Actions Frames Arrange Arrange Colors Address ContactsMailmerge Links Window Window Window Window Window Window Window HelpHelp Help Help Help Help Help Help Help Help Help Help IE BrowserOutlook Word FrontPage Excel Access Photodraw PowerPoint Publisher PaintProject WinExplorer

Menus synthesized in 508.2 are shown in Table 4, and have each instanceof menu type listed just once. Synthesized Main File Menu groupings are:File 508.1.1, Edit 508.1.2, View 508.1.3, Insert 508.1.4, Format508.1.5, Tools 508.1.6, Table 508.1.7, Data 508.1.8, Function 508.1.9,Window 508.1.10, and Help 508.1.11.

TABLE 4 Main Menu Synthesis - Twenty-Five Objects File Edit View InsertFormat Tools Table Data Function Window Help Favorites Image ActionArrange Search Colors Project Frames Address Effects Mailmerge LinksSlideshow ContactsFIG. 52 Simplified Menu Expressions

Table 5 Sample Unitary Main Menu Optional Arrangements shows aminimalist configuration with the same synthesis of twenty-five uniqueobjects shown in FIG. 51, but further simplified by grouping into fourmain menus.

TABLE 5 Sample Unitary Main Menu Optional Arrangements File Frame ToolFunction File Frame Tool Function View Edit Action Arrange Table InsertData Format Project Image Mailmerge Search Colors Slideshow AddressEffects Contacts Links Window Favorites Help

When menus are constructed using logical statements to associatesub-menus and functions, statements may specify any menu object in anygrouping. In macro, objects are groups of lines of code, that aregrouped functionally, and grouped programmatically, and groupedsystemically. There are hierarchical relationships between objectfunctions, and some objects have other objects as constituents, i.e. amain menu “has” sub menus and a sub-menu “has” other sub-menus orprogrammatic objects. Each term at each level of granularity isrepresented in a model Model of Everything 1000 with system identity:premier software suite, and terms can be grouped into main menus andsub-menus that suit users.

FIG. 52 illustrates Simplified Menu Forms 509 as a logical selectionstatement for a model of Model of Everything 1000 with the systemidentity: premier software suite as would allow selection at the programobject level with Program Objects 509.1.1, the menu object level withMenu Objects 509.1.2, and object level with Navigation Objects 509.1.3or other objects.

Shell With Simplified Menu Forms 510 illustrates the application ofunitary menu synthesis groupings to the selection of main file menusthat may be associated with shells 600.4. Simplified Menu Forms 509 andShell with Simplified Menu Forms go into Unitary Shell 601. NavigationBar 600.3 and Access 600.19 are also illustrated as optional menu objectelements.

FIG. 53 Unitary Platform

Platform for Everything 105 is made up of: UR-URL Identifier Method 101,Database of Everything 104, Unitary Shell 601, COTS or Open SourceComputer System 600.1, COTS or Open Source Shell Software With SimpleTools 600.7, COTS or Open Source Predicate Logic Software 600.8.Spreadsheet 600.5 and/or Database 600.6 software may also be used andare shown.

Platform for Everything combines the universal utility of Unitarycomponents and capacities with common programmatic forms and features inCOTS and Open Source tools in one unitary interoperable platform ofuniversal, persistent, infinitely extensible, identities.

In reality, real citizen identity is the platform for democracy. UR-URLIdentifiers 101 are real identity identifiers that correlate realcitizen identity with real referential incept ownership identity. Realidentity is the platform. Platform for Everything 105 is apparatus infour dimensions.

FIG. 54 Current Embodiment Access Process

Thus far figures have traced the deconstruction and reconstruction ofeverything as apparatus in five dimensions—0D to 4D. Abstractinformation infrastructure and architectural contexts have been madeconcrete as components and parts of physical apparatus. Figures haveshown how parts fit together and how parts work together to form oneuniversal Model of Everything 1000. Civil and economic dimensions havebeen considered mechanically. The following figures address the accessprocess component of |EVERYTHING| which includes the politics of accessand control, but without which, Model of Everything 1000 would not be|Everything|. The point of identifying, describing, and co-locatinginformation resources is so people can find and use them. Access ispivotal.

Process flow diagrams that follow share common steps which, oncedescribed, are referred to by Part No. in subsequent diagrams, and notdescribed again in detail.

FIG. 54 depicts the Current Embodiment Flow Diagram 511 which beginswhen people and things are instantiated at incept with Official InceptAuthentication 101.4.1. Real Names 101.2.2 are associated with realidentity in “the system”. “The system” refers to that Western Democraticinstitution that comprises “We the people”, the body politic, where theindividual elements in the system are Sui Juris 309.9.1 citizens orNon-Sui Juris 309.9.2 citizens with system identity: USA (or othercountry) which has sovereign interest in and responsibility formaintaining a public roll of authenticated citizen identities—Real Names101.2.2.

Sui Juris citizens may participate in the economy, may make contractsfor goods and services, may vote, and may otherwise self-represent inthe extended marketplace of country of origin. Armed with proof ofidentity—simple birth certificate and picture ID, a person can travelfreely in country, get a drivers license, get a Social Security Numberand get a job, open bank accounts, get utility service, phone service,television service, and service of all kinds. He can use publictransportation, public libraries, and use public services. Identity in“the system” means access to critical public infrastructure owned incommon by the citizenry, held in trust and managed for the people by the“current administration”.

Thus, people may contract with vendors to obtain access to the telephonesystem, access to cable systems, to banking systems, or other servicesystems, and particularly, access to the Internet. Vendors MintArtificial Identifiers 500.2 after either No Authentication 500.3 orAuthentication 500.4, which assigns a User ID/Password 500.6, that givesAccess 600.19 to Vendor Service Providers 500.7.

Layers 500.5 includes the growing number products and services fromAuthentication Schemas, and Authentication Products, to Privacy andSecurity Products and Certificates, Federation Partners, and WebServices.

Once access identity is established, and User ID/Password 500.6formalized, users can access their accounts, buy, receive vendorservice. In the case of the Internet, access is to the largermarketplace of Vendor Service Providers 600.7. Part 600.7 signifiesparticipation in the economy, which is the desired end step.

FIG. 55 Web Services Vendor Mint Access Process

The Internet is fast becoming the only system as more and more businessis conducted electronically through ever widening arrays of devices andexponentially increasing volumes of transactions. Identity Federationsafford business many interoperability improvements, includingparticipation in one system of unique identifiers. Just as universalutility is achieved through UR-URL Identifiers 101.1 for everything, sobusiness partnerships in supply chains achieve the same utility but on asmaller scale.

New Web Services Vendor Mint Model Flow Diagram 512 depictsinstantiation 101.4 preceding identity 101.2.2 followed by Vendor TrustProvider 500.8, such as Liberty Alliance and UDDI, which relies onAuthentication By Vendor 500.4 and Layers 500.5 of authenticationproducts and services, culminating in Vendor Mint Artificial Identifier500.2 and Access 600.19.

An important distinction of this flow process as compared to flowprocesses 511, 513, and 514 is shown in the sub-loop through VendorAuthentication 500.4 and Vendor Anytime Authentication 500.9. to VendorService Provider 500.7. In the new federated web services model, vendorpartners serve as Trust Providers and authenticate identities for theirpartners, supply chains, and customers.

Official Authentication 104.2 is missing. Moreover, the anytimeauthentication necessary to conduct online transactions bypasses theuser altogether.

FIG. 56 Worst Case Future Vendor Mint Access Process

The only thing worse than vendor trust providers owning private identityis depicted in Worst Case Future Vendor Mint Model Flow Diagram 513.Diagram 513 is identical to Diagram 512 as regards the flow from 101.4.1to 101.2.2 to 500.8 to 500.2 to 600.19 to 500.7.

As noted, the difference is in the sub-loop through OfficialAuthentication 101.4.2 and Official Anytime Authentication 101.4.3. Theuser is again bypassed, but this worst-case scenario shows vendorsinteracting directly with official authentication processes, positioningvendors squarely between citizens and their government.

FIG. 57 Present Invention Access Process

Present Invention Owner Self-Mint Flow Diagram 514 depicts instantiation101.4 preceding identity 101.2.2 followed by Official Authentication101.4.2 provided directly to the user-maker-owner making a claim to MintReal Identifier 500.1 in Model of Everything's 1000 public domain.User-maker-owners may Access 600.19 the Internet and Vendor ServiceProviders 500.7, as well as initiate Official Anytime Authentication101.4.3 to vendors.

FIG. 58 Access Process Comparison

FIG. 56 shows all four flow process diagrams, 511-514 aligned forcomparison. The distinction between authentication steps is significant.Without self-minting, the only choices are vendor mints or a nationalmint, owned and controlled by the government. Without the presentinvention, the worst is inevitable with vendors churning out privacysolutions as fast as government is automating vital public domains.

FIG. 59 Direct Ownership Process Components

FIG. 59 illustrates detail in Current Embodiment Flow Process 511.

Our current analog system is a system based on Private Ownership 500.10of Real Identity, Real Property, Personal Property, Tangible Property,Intangible Property, and Intellectual Property.

-   -   500.11 We are owners in common with Public Infrastructure        Ownership 500.11 of Public Property, including but not limited        to Public Resources, Public Broadband, Public “Hot Spots”,        Public Television Broadcast, Public Radio Broadcast, Public        Library System, and Public Mail System.    -   500.12 We have Privately Owned Systems 500.12 including but not        limited to Computers, Monitors, CPU/OSes, Storage Media,        Peripherals, and Software Licenses that are our private        property.    -   500.13 We also own Access Devices 500.13 such as Cell Phones,        Landline Phone, Walkie-Talkie, Television, Radio, Ham Radio        devices, Broadband devices, GPS Receivers, and Satellite Dishes.    -   500.14 We have service contracts with Access Vendors 500.14        including but not limited to Phone Company, Cable Company,        Wireless Company, Cellular Company, Internet Company, Satellite        Company, Digital Audio Company, GPS Company, Broadband Company,        and Mail Delivery Company.    -   500.15 Vendors use customer identity as Access Means/Control        500.15 which takes various forms including but not limited to        Phone Number, User/Account Number, Wireless Number, Cellular        Number, User ID/Password, User Name/Account Number, User/Account        Number, and Name/Account Number.    -   500.16 Users buy and own products, and rent access and services        from multiple vendors in a competitive marketplace with        individual Service Contracts 500.16 made between        user-maker-owners and individual vendors for specific uses.        FIG. 60 Intermediary Ownership Process Components

In the New Web Services Vendor Mint Model 512, there is VendorInfrastructure Ownership and Control 500.17 in Television, Radio,Broadband, Telephone, Internet, Cable, Optical Cable, Cellular, andMicrowave. The new model relies on early obsolescence ofvendor-dependent devices with vendor embedded controls and single-vendoroperating instructions. The new model actively promotes Rented Hardwareand Access Devices 500.18 including but not limited to Rented AccessHardware, Proprietary RF Receivers, Proprietary Cable Receivers,Proprietary Satellite Receivers, Proprietary Broadband Receivers,Proprietary Digital Audio Receivers, Proprietary GPS Receivers,Proprietary Data Receivers, Rented Identity, Rented Web SoftwareServices Access, Rented Web Service Product Access, Rented Web ServiceTime Access, Rented Web Service Data Storage Access

The new Access Vendors 500.19 are Identity Federations, who useFederated Identity for Access Means and Control 500.20 that establishVendor Control of Private Identity, Vendor Control of PrivateInformation, Vendor Control of Private Devices, and Vendors BetweenCitizens and Government. In place of many service contracts with manyvendors, the new model is Federated Web Services 500.21 and theirproduct is Trust, embodied as Communication Services, AuthenticationServices, Privilege Management Services, Security Services, ApplicationServices, Directory Services, Hosting Services, and Search Services, allin one Membership Contract and End User License Agreements (EULA's) withOne-Sided and Hidden Terms and Conditions, and Personalization with UserProfiling/Data Mining and Content Pre-Screening/Filtering.

FIG. 61 Ownership Process Components Comparison

FIG. 61 illustrates the differences between Owner System—IndividualOwnership—Direct Access 515, comprised of the Current Embodiment FlowDiagram 511 enhanced by the Present Invention Owner Self-Mint FlowDiagram 514, and the New Web Services Vendor Mint Model Flow Diagram512.

The New Web Services Vendor Mint Model 512 is based on the unsupportablepremise of vendor ownership of private identity, and, absentalternative, will place Middle-Men 500.24 between Citizen 500.22 andGovernment 500.23, where the Present Invention Owner Mint Model 514sustains and builds upon the fundamental covenant between Government500.23 and Citizens 500.22.

The current embodiment is a real world analog system based on privateidentity ownership. The Internet embodiment and its evolving new form,Federated Web Services 500.21, replicates the real world as anelectronic system based on vendor identity ownership. This is a hugelysignificant shift in premise. The resultant Vendor Mint Model 512requires Layers 500.5 of authentication products and services to correctproblems created by artificial identity in the first place. A system ofartificial identities cannot sustain anything, much less everything. Theelectronic version of “The System” must be as real as its analogoriginal. The economy depends on it.

The present invention corrects fundamental flaws in the currentelectronic embodiment by providing method, means, and apparatus based onprivate identity ownership, thus bringing the electronic replica intoalignment with its analog original.

VI Web Portal to Everything View 5

FIG. 62 Web Portal to Everything Components

The components of Web Portal to Everything 106 are: UR-URL IdentifierMethod 101, Platform for Everything 105 including all parts, NavigationBar With Links 600.3, COTS or Open Source Web Page Software 600.9, COTSor Open Source Browser Software 600.10, Frames With and Without Content600.18, and Access 600.19.

FIG. 63 Web Portal View

FIG. 63 illustrates a common web portal form apparatus made up of COTSor Open Source Computer System 600.1, Navigation Bar With Links 600.3,COTS or Open Source Web Page Software 600.9, COTS or Open Source BrowserSoftware 600.10, Frames With and Without Content 600.18, and Access600.19.

FIG. 64 Unitary Web Portal

Web Portal to Everything 106 is made up of a common web portal formapparatus as shown in FIG. 63, and made up of 600.1, 600.3, 600.6,600.9, 600.10, 600.18, and 600.19, plus Unitary components 101, 104, and105 which include Unitary Shell 601, Unitary Ontology 300, and UnitaryRDF 400, not called out separately in FIG. 64.

Web Portal to Everything 106 is depicted as a user view of computermonitor with Platform for Everything 105 open in the background toDatabase of Everything 104, and with a Web Portal to Everything 106browser frame open in the foreground.

Web Portal to Everything 106 embodies Model of Everything's 1000cumulative aggregation of unitary components: Unitary ReferenceArchitecture 100 with UR-URL Identifier Method 101, List 102, Table 103,Database 104, Platform 105, and Web Portal 106 to Everything, includingUnitary Ontology Architecture 300, Unitary Resource DescriptionFramework 400, Unitary Process Architecture 500, and Unitary Apparatus600.

Web Portal to Everything 106 is Model of Everything's 1000 electronicreplica of our global network of information, transportation, andtelecommunications systems—all systems in one system, replacing manysystems of artificial access identifiers with one system of universalreal identifiers minted by citizens, owned by citizens, controlled bycitizens, authenticated as in analog by citizen's official channels, andused by citizens to identify person and property during the course ofself-representation in democracy and participation in the economy. WebPortal to Everything 106 is apparatus in all dimensions.

FIG. 65 Sample Web Portal to Everything Page 1

FIG. 65 depicts a sample Web Portal to Everything 106 page made up of600.1, 600.3, 600.6, 600.9, 600.10, 600.18, and 600.19, 601, 101, and104 with Frame Contents 600.18 illustrating Database of Everything 104as might be accessed by a user looking for information, informationwhich in this and subsequent samples corresponds to examples given inthe specification about homes in Podunk County.

FIG. 66 Sample Record 1

FIG. 66 illustrates a sample Model of Everything 1000 object record suchas would correspond to an Official Record of Ownership 414.1.

FIG. 67 Sample Record 2

FIG. 67 illustrates a sample Model of Everything 1000 object record suchas would correspond to an Individual Public claim 414.2.

FIG. 68 Sample Record 3

FIG. 68 illustrates a sample Model of Everything 1000 object record suchas would correspond to a Vendor claim 414.3.

FIG. 69 Sample Record 4

FIG. 69 illustrates a sample Model of Everything 1000 object record suchas would correspond to an Individual Update Record 414.4.

FIG. 70 Sample Record 5

FIG. 70 illustrates a sample Model of Everything 1000 object record suchas would correspond to a Public Directory Record 414.5.

FIG. 71 Sample Record 6

FIG. 71 illustrates a sample Model of Everything 1000 object record suchas would correspond to an Original Incept claim 414.6.

FIG. 72 Sample Record 7

FIG. 72 illustrates a sample Model of Everything 1000 object record suchas would correspond to an Official US Census Record 414.7.

FIG. 73 Sample Record 8

FIG. 73 illustrates a sample Model of Everything 1000 object record suchas would correspond to a Personal Record 414.8.

FIG. 74 Sample Record 9

FIG. 74 illustrates a sample Model of Everything 1000 object record suchas would correspond to a Personal Homepage 414.9.

FIG. 75 Sample Record 10

FIG. 75 illustrates a sample Model of Everything 1000 object record suchas would correspond to search results for John Q. Public and 123 PalmyWay 414.10.

FIG. 76 Sample Records Summarized

FIG. 76 depicts a summary of Sample 414 records illustrated in FIGS. 66through 75, Parts 101, and 414.1 through 414.9, as might be representedin Unitary Reference Architecture 100 tabular apparatus forms.

FIG. 77 Sample Web Portal to Everything Page 2

FIG. 77 depicts a sample Web Portal to Everything 106 page made up of600.1, 600.3, 600.5, 600.9, 600.10, 600.18, and 600.19, 601, and 101,with Frame Contents 600.18 illustrating Table of Everything 103 as mightbe presented to as user as search results based on specification Samples414 of records in Podunk County.

FIG. 78 Enterprise Record Examples

FIG. 78 depicts a summary of enterprise records as might be representedin Unitary Reference Architecture 100 tabular apparatus forms withUR-URL Identifiers 101 in a system that applies the principle ofownership in a business asset management context. Enterprise SummaryArray 415 is made up of hierarchically related object records thatrepresent hierarchical entity roles within an enterprise which “have”resources, relations, responsibilities, and other properties and valuesthat each have identity object records in an enterprise model of Modelof Everything 1000 and extended Unitary RDF 400.

Enterprise Summary Array 415 is made up of object arrays correspondingto Company 415.1, Component 415.2, Division 415.3, Department 415.4,Work Center 415.6, and Work Station 415.6.

FIG. 79 Enterprise Record Example Detail

FIG. 79 depicts the same enterprise information as depicted in FIG. 78,but with more and or different detail. Model of Everything's 1000dimensional construct supports any level of granularity, as illustratedby comparison of FIGS. 78 and 79.

Enterprise Detail Array 416 is made up of object arrays corresponding toCorporation 416.1, Component 416.2, Division 416.3, Department 416.4,Work Center 416.5, Work Station 416.6, Resource 416.7, Role 416.8, andProcess 416.9.

FIG. 80 Present Invention Part List Example

FIG. 80 illustrates the present invention's parts list as might berepresented in Unitary Reference Architecture 100 tabular apparatusforms with UR-URL Identifiers 101. Part Number Array 417 showscorrespondence between six terms required to describe parts and sixterms of UR-URL Identifier Method.

Part Number Array 417 is made up of FIG. No/Path 417.6, Part No./UR-URL417.1, FIG. Name/Owner 417.3, Part Name/Name 417.2, Sub-Parts/Keywords417.5, and Parent Component/Authority 417.4.

FIGS. 81-92 Prototype Illustrated

The utility, practicality, and universality of the present invention maybe most comprehensively illustrated in a prototype web portal. A modelof records of claims of everything, including event objects and eventassertions, could be made manifest in other media, and could be depictedwith additional detail in both content and active object design. TheUR-URL prototype is intended as an illustration only, simple and short,and as such is not intended to represent all possible illustrations.

The actual technical construction of the apparatus itself is elementary,compared to its principles of organization. It was designed only afterthe indexing and classification system had been developed. A model ofeverything is a lot of stuff to organize on a few pages. The ontology isthe result of much consideration, and its simple framework is evident inthe information groups and layouts.

The prototype UR-URL website apparatus was designed in 2001, in order todemonstrate functional utility. A second prototype front end wasdesigned in March of 2002 in order to demonstrate commercial, social,and political utility. FIGS. 81/96 to 92/96 depict the originalconceptual rendering.

Prototype Structure

Everyday persons may construct a functional version with COTS hardwareand software, i.e. Microsoft Word Web Page Complete front end withlinked Excel worksheet back end where records are added through an Exceltemplate and Search performed with built-in “Find” functionality.Persons skilled in the art may construct functional versions withvarious COTS and proprietary authoring programs. Homepage views aresample depictions as might be developed and are intended to illustratebut not specify interface or application.

FIG. 81 Homepage 1

FIG. 81, Homepage 1, represents the initial web portal user interface.The purpose of Homepage 1 is to provide links to direct visitors tofrequently asked questions, and to promote applications partners.

FIG. 82 Homepage 2

FIG. 82, Homepage 2, represents an overview of the web portal and itsservices.

FIG. 83 Homepage 3

FIG. 83, Homepage 3, continues the representation of the utility andfunctions of the web portal and its services.

FIG. 84 Homepage 4

FIG. 84, Homepage 4, represents a high-level graphical map of the webportal architecture.

FIG. 85 Homepage 5

FIG. 85, Homepage 5, represents the inclusion of generic terms of useand various policy statements, but does not stipulate contract languagein entirety. The purpose of Homepage 5 is to illustrate conformance totypical web portal features. Details of such policies areinconsequential to the utility of UR-URL Addressing and indexing method.

FIG. 86 Homepage 6

FIG. 86, Homepage 6, represents an introduction to the commercialutility of UR-URL, providing general information about how applicationsmay be considered. Groupings are intended to illustrate broad categoriesof technical functions.

-   -   1. “Official records” depicts UR-URL's utility as a compendium        of record able public information and combines legal filings,        product registration, birth and death recording, certifications        and so forth into one system of official records of claims.    -   2. “Communications services” depicts UR-URL's utility as a        compendium of global positioning and locating address protocols,        and combines many address protocols for traffic control, voice        and data telephony, and so forth into one system of addresses        for routing communications and communications signals.    -   3. “Group services” depicts UR-URL's utility as a compendium of        references, and combines directories, search engines,        registries, cross-referenced multi-source personal profile data,        and so forth into one system of addresses for correlation and        integration by/with individual entities, groups, and/or their        associated data.    -   4. “Data services” represents UR-URL's utility as an integration        platform, and combines image mapping, synthesis, conversion,        translation, correlation, projection, replication, reproduction,        archival storage, and so forth into one system of unique control        elements.        FIG. 87 Homepage 7

FIG. 87, Homepage 7, represents UR-URL's utility as a gateway forindividual entities to connect with one another as well as to controlhow information about them is collected, stored, and disseminated.Homepage 7 depicts one future application that utilizes user-driven datamining and instant messaging technologies in real time, assigningaddresses to information strings as specified by users for their ownprivate information agent purposes. HomePage 7 does not stipulate allpossible illustrations, rather is intended to show how technologies maybe combined and integrated through the use of UR-URL addressing andindexing method.

FIG. 88 Homepage 8

FIG. 88, Homepage 8, represents the record registration function withclassification options, and an automated form that shows relevant datafields and selections.

FIG. 89, Homepage 9

FIG. 89 Homepage 9, represents an overview of a typical search utilitywhere public users may search the entire database. Sample pages areintended to illustrate general search functionality, and are notintended to stipulate all possible illustrations of searchfunctionality. In the present illustration, anonymous searches arefacilitated through the use of temporary UR-URL ID codes; simple andadvanced search options enable selection specification.

FIG. 90 Homepage 10

FIG. 89 Homepage 9 FIG. 90, Homepage 10, continues the representation ofa typical search function.

FIG. 91 Homepage 11

FIG. 91, Homepage 11, represents UR-URL's commercial utility whereapplications vendors' products and services correlated to UR-URL areaccessed by the public.

FIG. 92 Homepage 12

FIG. 92, Homepage 12, represents UR-URL's utility an illustration of thevalue equation derived from public-private partnership. UR-URLaddressing and indexing properties have universal applicability and assuch provide an ideal standard nomenclature for linking individuals andvendors with disparate systems and data. Users require uniqueidentification and desire convenience; vendors must provide uniqueidentification and UR-URL provides convenience. Increasing needs forinteroperability at every level can be met through natural three-waydemand/supply partnerships, such as those illustrated in FIG. 92Homepage 12, that generate value all parties.

FIG. 93 Alignment Between Components and Component Parts of UnitaryReference Architecture

FIG. 93 shows the progressive development of Unitary ReferenceArchitecture 100 components, beginning with UR-URL Identifier Method101.1, which goes into List of Everything 102, which goes into Table ofeverything 103, which goes into Database of Everything 104 which goesinto Platform for Everything 105 and Web Portal to Everything 106.

FIG. 94 Alignment Between Parts and Part Numbers of Unitary ReferenceArchitecture

FIG. 94 shows the relation between the Several Dimensional Views I-VIand the part number coding schema correlating components and parts 1000,100, 200, 201, 202.1, and 201.2.

FIG. 95 Sample Embodiment Apparatus

-   -   FIG. 95 illustrates apparatus parts and part numbers used in        descriptions and figures:    -   600.1 COTS or Open Source Computer System    -   600.2 Event Data    -   600.3 Navigation Bar With Links    -   600.4 Shell    -   600.5 COTS or Open Source Spreadsheet Software With Search and        Hyperlinks    -   600.6 COTS or Open Source Database Software    -   600.7 COTS or Open Source Shell Software With Simple Tools    -   600.8 COTS or Open Source Predicate Logic Software    -   600.9 COTS or Open Source Web Page Software    -   600.10 COTS or Open Source Browser Software    -   600.11 Tabular Architecture Rows and Columns    -   600.12 Infinite Integration With UR-URL Identifier Method Scope    -   600.13 Infinite Range With Infinite UR-URL Identifier Method        Scope    -   600.14 Finite Integration With Finite Identifier Method Scope    -   600.15 Variable Relational Tables    -   600.16 Finite Range With Finite Identifier Method Scope    -   600.17 Variable Columns    -   600.18 Frames With and Without Content    -   600.19 Access    -   600.20 Common Architectures    -   600.21 Vendor Ownership Web    -   600.22 Private Ownership Web    -   600.23 Website, Search Engine, and Directory of Everything in        the Public Domain    -   601 Unitary Shell        FIG. 96 Sample Embodiment

FIG. 96 represents an embodiment of the present invention, Model ofEverything 1000, with main components made up of Unitary ReferenceArchitecture 100—made up of UR-URL Identifier Method 101, List ofEverything 102, Table of Everything 103, Database of Everything 104,Platform for Everything 105, and Web Portal to Everything 106—, UnitaryInfrastructure 200, Unitary Ontology Architecture 300, Unitary ResourceDescription Framework (RDF) 400, Unitary Process Architecture 500, andUnitary Apparatus 600.

VII Event-Oriented View—Architectural Dimensions

An event-oriented semantic data method, model, and resource descriptionframework representing a system of information event claims. The presentinvention has the distinction that RDF Array (RDF Array 400) applies toevents irrespective of embodiment type, also called event states(404.5), comprising Person (301.5), Property (301.6), Principle (301.7),and Transaction (301.8). The system may include a storage deviceconfigured to store a plurality of files and a file system configured tomanage access to the storage device and to store file system content. Inone embodiment, the semantic model may comprise tabular apparatus. Inanother embodiment, the semantic model may comprise predicate logicn-tuple statements and concept graphs. In other embodiments, thesemantic model may comprise field labels for identifying, addressing,indexing, and organizing event records in digital and physical formats.

FIG. 97 Unitary Object Identity Array

Each object has a unique set of XYZT designations that correspond to anestablished standard “address” (many equivalent formats). UR-URLprovides one common database field and one common nomenclature todescribe the one thing that everything has in common—incept. When inceptevent location and time are stipulated in terms ofmaker-owner-discoverers' claims to origination and ownership, it's aunique name in recorded history and instantiation matches real-worldlegal standards. Geocoordinates are numbers which are not patentable butwhich are freely available for application, indeed many prior artsincorporate geocoordinates in object-oriented identifier schemas. Thenovelty and utility of the present invention derives from thecombination of XYZT spacetime coordinates as one field of six in anevent-oriented resource description framework. Because time isinfinitely extensible to the extent that numbers are infinite, andbecause space is infinitely granular to the extent that numbers areinfinite and universal, relative referential geocoordinates are alsoinfinite and universal, therefore Unitary Object Identity Array isaccordingly infinite and universal.

FIG. 98 Unitary Event Identity Array

Unitary Event Identity Array comprises Unitary RDF Array Part No. 400,which comprises a position description element (Identifier 401), a pointdescription element (Identity 402), an observer description element(Origin 403), a specification description element (Agreement 404), ascene description element (Constituents 405), and a reference-bodydescription element (System 406). Where the XYZT identifier field alone(401) differentiates each event from every other event, Unitary EventRDF Array's (400) particular six elements in combination comprise aunique identifier that differentiates each event description from everyother event description. Multiple claims about same events share sameidentifiers but have different assertions, which represents afundamental shift away from standard object oriented practice to anevent orientation. The semantic model may be optimally represented insix terms for public systems (401-406), eight terms for enterprisesystems (401-408), or in any combination of terms in addition toIdentifier 401 for private systems, and in tabular, tuple, and otherformats.

FIG. 99 Unitary Ontological Architecture

Each thing in |Everything| is defined by Albert Einstein, and alsoherein by the present invention, as an event. According to Unitary TopLevel Ontology 301.1, event condition is either objective or assertiveand event states are person, property, principle (idea), andtransaction. Duality is resolved by symmetry in that event objects andevent assertions share identity-identifiers. |Everything| comprisesclaims—assertions of event description—claims are incept events. UnitaryTop-Level Ontology sets terms for instantiating event condition, state,and class. Unitary Integrated Ontology 309 has extensible primitives in4-D: concept, point, event, object.

FIG. 100 Unitary Apparatus Structure

The most common apparatus of information systems are tables and lists.Information architecture specifies how entries are identified,described, and related. The “container materials” to “make” a tableapparatus are rows and columns. Utility depends on how well the columnfield labels, known as Resource Description Framework (RDF), aredesigned to capture shared attributes of list objects.

FIG. 101 Unitary Event RDF Architecture

Semantic information architecture specifies data kinds and organization.The only mandatory element is the unique identifier. System size islimited by the quantity of identifiers available. Common identityalgorithms are finite; Unitary Identity is not.

FIG. 102 Comparison with Common Architectures

Standard object oriented practice is many different systems anddifferent architectures. Common architectures typically segregate bydata type and/or use because each type of resource has its ownparticular terms of description. A phone directory of people has columnsfor name, address, zip code, and phone number; a sales database hasfields for product names and details; and an equipment listing hascolumns for model numbers, sizes, capacities, cycle times, and so forth.

FIG. 103 Integration with Common Architectures

You can merge tables as long as each element in the combined list hasits own unique identifier, but the description fields can rarely bemapped directly one-to-one. Equipment doesn't have zip codes and peopledon't have sales prices but the new combined table has to have bothfields. You end up with way too many columns. Integration with commonarchitectures takes many fields. Integration with Unitary EventArchitecture (UEA) takes only six fields, the minimum to uniquelydifferentiate, describe, and discover each event.

FIG. 104 Event Oriented Semantic Structure Illustrated

414 Samples [FIG. 76] with circles superimposed illustrate multipleevent claims sharing same identifiers. Common semantic architectureswould show only one record per unique identifier. Boxes superimposedillustrate two claims for the same event, the listing of a home. Realtoridentifier is not the owner's property identifier but the transactiondate/time is the same. The XYZ's are different but the T is the same.

FIG. 105 Enterprise Information Asset Embodiments

The present invention reduces “big data” management to simplest termsand processes with one information architecture for the entirecomplement of enterprise resources regardless of product, service,function, resource type, or corporate organization. Every file, folder,document, and user—every activity, system, operation and element—everykeystroke—is an event that can be instantiated as either Person,Property, Principle, or Transaction, and furthermore can be listed anddirectorized with six universal terms of description. Business isn'talways tidy—things change—change happens to individual resources, and togroups and types of resources—new conditions are just new tags andvalues

FIG. 106 Enterprise Information Asset Ownership

Ownership scales from people to policy to process to product—it's themost common basis for fiscal accountability, i.e. roles fromtop-to-bottom own resources, scopes of work, and budgets—“who owns what”is the key criterion and the key operator is “has” (“∩”).

FIG. 107 Sample Enterprise Information Asset Functions

Using eight fields for enterprise records more closely aligns withbusiness functions where resources and roles are commonly defined inthose terms. This illustration [Table 2 with colloquial terms added]shows sample “Has Category” fields that might be used in an enterpriseinformation asset management event system database. Each superclassrepresents a union set [Identifier∩ Set (Code, Value)(Code, Value) . . .] where codes are class, category, and type labels drawn from theontology and values are object-specific properties and attributes.

FIG. 108 Enterprise Information Asset Management

Resources are manpower, materials, and methods (or people, property,principles). Activity is a transaction with an identifier, name, owner,authorizing instrument, path, and keywords that specify predecessor andsuccessor relations. A Critical Path Network with the “where” and “when”resources will be deployed already embedded in the identifiers isparticularly useful for enterprise applications.

FIG. 109 Comparison Between Webs

The current version of our web has layers of intermediaries betweenusers and the policies and standards that determine what informationthey can view, how much information they can exchange, and who they canshare with.

We have vendor ownership and control of private identity. we want publicaccess to our public resources—our bandwith, our airwaves, our publicrecords, our public infrastructure. We want real world principles ofprivate ownership applied in the digital version of our socio-econimicsystems. We want autonomous control of identity and information assets

FIG. 110 Exemplary Embodiment—Unitary Semantic Web

An Exemplary Embodiment is framed as an independent global publicinformation systems network and semantic web with searchable onlinedirectory and registry of incept event ownership claims made by ownersabout their person, property, ideas, and transactions. The components ofUnitary Semantic Web include an information system (600.24) likened toprior art systems (FIG. 60) such as AOL, UDDI, Liberty Alliance, Yahoo!,Google, et al. (512), delivered in a common semantic web service portalapparatus (600) using common commercial off the shelf hardware,software, and storage media (600.1), common public accessibilityinfrastructure (600.19), common search engine utility (600.5), commononline browser interface (600.10), and common tools (600.3 through600.11) , to make an information system (1000) for users that features aphone-book-like directory (FIG. 65) of user-maker-owner-published (FIG.61) searchable, sortable, updateable, discoverable information records(600.2).

Present functional capacities and unique interoperational synergies areachieved through specific combination of specific architecturalcomponents defined in the present specification and depicted in presentdrawings, comprising:

-   a) the precise definition of the network system identity    (information incept-origination events) (1000)-   b) the capacity of the specific identity criterion defined    (incept-origination claim 100)-   c) the capacity of the specific organizing basis defined    (incept-origination event ownership) (200)-   d) the capacity of the specific ontological structure defined    (derived from relativity) (300)-   e) the capacity of the specific field labels defined (derived from    synthesis) (400)-   f) the capacity of the specific addressing schema defined (incept    origination event coordinates, in any of numerous equivalent    standard formats) (100, 500, 600)

All subcomponents are required to make each component and all componentsare required to make the present invention. No prior arts have allpresent components, and no prior arts employ components in presentcombination to present purpose or with present resultant combinedfunctionality or utility.

FIG. 111 Block Diagram of Computing Module

A depiction of a typical computing module which might contain but is notlimited to such elements as Bus 703, Processor 704, Memory 708, StorageDevices 710, Media Drive 712, Media 714, Storage Unit I/F 720, StorageUnit 722, COMM I/F 724, and Channel 728.

FIG. 112 Block Diagram of Labeling Process

The process of labeling (Part No. 740) an unlabeled event (Part No.740.1) may be performed by non-transitory computer executable programcode (Part No. 740.3) configured for receiving (Part No. 740.2) therepresentation of an unlabeled event, and labeling (Part Nos.740.4-740.7) it with ontological primitive terms (Part No. 309)according to Relative Event Ontology (Part No. 302) with point,reference-body, observer, position, scene, and specification descriptiveelements, and according to Unitary Event Ontology (Part No. 301) withperson, property, principle, or transaction state or class elements, andthen storing (Part No. 740.8) the labeled event in non-transitorycomputer storage medium (Part No. 740.9).

FIG. 113 Sample Listings of Claims to Event Ownership

Unitary Reference Architecture defines and applies UR-URL relativereferential geotemporal xyzt coordinates as unique resource identifiers(URI) within a claims-based system of incept ownership event records.Thus constrained UR-URLs can function as all-purpose identifiersapplicable to not only physical geography and geo-information, but alsoto people, things, ideas, and activity, as well as the transactions thatformalize agreements about them-everything-all events in everyday life.Events are either objective or assertive, that is, things or ideas.Framed as claims to event incept ownership, people can associate theirperson, their property, their principles (ideas, values, opinions,thoughts, etc.), and their interactions with the time and location ofthe occurrence.

Sample Labeled Claims (Part No. 750) comprises a selection differentclaims (Part Nos. 750.1-750.5) illustrative of events that may bedescribed, listed, labeled, and integrated with Unitary ReferenceArchitecture's UR-URL Identifier Method (Part No. 101).

Subcomponents grouped by topic name. Part No. 750.1 Rock Concert showshow many different claims about the same event can share the sameidentifier - same location, same time, in this case, the concertlocation and date/time. Part No. 750.2 Human Thinking shows how Person 1can claim his own ideas himself, and at the same time have a physicalmonitor that reports sensor data about Person 1's state of satiety to avendor, who presumably analyzes his state of being. Part No. 750.3 showsdifferent claims about the event of Sky from different makers atdifferent locations and times. Part No. 750.4 is a particularlyinteresting example. It shows that where many people believe in God, andmany churches have perspectives on God, as to the permanent publicrecord, the existence of God is a claim with different makers andpositions. Part No. 750.5 also speaks to a domain not commonly thoughtof as serious or recordable, yet fortune telling certainly can becaptured as claims to event ownership, again different makers andpositions. Part No. 750.6 rounds out the example with detail from ahypothetical fortune telling website, a la Madame Cleo - Call Me Now!These represent internal company records and have identifiers keyed toparent, same base but different extensions.

Mme Cleo's products/services are Tarot Readings and P2P consultations.Tarot is a system that draws conclusions about a subject by accessing,sorting, selecting, and combining various sets of event attributes asrevealed on cards during the “reading” process. Mme Cleo's corporateinformation assets are well defined. Tarot is a system of about 50elements in three classes (Major and Minor Arcana, Archetypes), eachwith an assumed limit of 20 attributes, or qualities andcharacteristics. Each quality and characteristic may be considereddiscrete and definable in key words and other descriptive fields.Inference is drawn from user-selected card combinations. For thepurposes of this illustration, two types of inference are possible: 1)inference from the individual cards taken in isolation, and, 2) additivevalue of individual pairs, triads, and in total. Each instance ofinference may be associated with the element itself as additionaldiscrete descriptions. Total quantity of uniquely differentiable listitems is assumed to be around 1,000,000 records. This entire system ofdefinitions and relationships can be defined, listed, labeled, andaccessed pretty easily.

There is no mystery. First stage development efforts would include firstformalizing her system of definitions, and then purchasing and loadingeach of the sets of definitions from the dozens of off-the-shelf booksavailable through Barnes and Noble. Cross reference all of it, and youhave a Tarot Search Engine. Once the back end database has beenpopulated, and the portal front end is in place, all she has to do isadd her URL to the commercials and start saying, “Log-on now for yourfree tarot reading . . . ” In this simple application, users selecteither a personalized reading, which asks for some user specifiedparameters that add customization through choice of “layouts” and randomor user specified card elements. Results are personalized and displayedfor a fee.

Why would a fortune teller care about recording ownership of claims?What “property” would she register? She would record ownership of herideas: the database elements, as a set of defined system elements thatshe invested time in gathering and making accessible are intellectualproperty. Each of the 1,000,000 individual discrete definitions (1, 1+2,1+2+3 . . . ) is a claim of meaning Cleo owns the concept, the system asa whole and the elements within the system. They are copyrightable,remarkable, and the system itself might be patentable.

Madame Cleo's internal database uses UR-URLs for customer ID numberswhich corresponds to actual real people as research subjects. WhenMadame Cleo completes an electronic contract, there is a record of theuser and the values generated for and about that user. It constitutes asnapshot in time of a conclusion and/or a prediction. Regular userfeedback and updates constitute a growing knowledge base oftestimonies—claims—as to whether the forecast was right or wrong. Aseries of entries could comprise a user profile that could be tested andvalidated. While “proof” hinges on personal interpretation andattestation, as responses are collected, studied, correlated, andrefined over time, heretofore-unknown patterns could emerge with dataanalytics. One permanent ID provides an absolute reference point fromwhich to confirm or disprove the systems' accuracy over time.

FIG. 114 Unitary Tools

Reference architecture means the identity metasystem—how all theindividual elements in an information system areoperationalized—principally, the unique identifiers. Referencearchitecture also refers to the descriptive terms and their structure asfield names/column headers, and to the specified complement of standarddata labels. These are the three essential ingredients for tables anddatabases.

The term Unitary Reference Architecture and acronym URA refer to thecombined toolset comprising:

-   -   1. Unitary Identity Architecture (UR-URL) for identity (Part No.        100);    -   2. Unitary Infrastructure for foundational definition (Part No.        200)    -   3. Unitary Event Architecture/Resource Description Framework        (UEA) for field names/column headers (Part No. 300);    -   4. Unitary Ontology Architecture (UOA) for data labels (Part No.        400);    -   5. Unitary Process Architecture for programming (Part No. 500);    -   6. Unitary Apparatus for delivery (Part No. 600).        FIG. 115 Concept Map

A concept map is a diagram that depicts suggested relationships betweenconcepts, which can be articulated in linking phrases such as “causes”,“requires”, or “contributes to”. It is a graphical tool that designers,engineers, technical writers, and others use to organize and structureknowledge. FIG. 115 depicts one aspect of the present invention, therelation between Event, Claim, and Description.

List of Reference Numerals Part No. Part 1000 Model of Everything 100Unitary Reference Architecture 1.1 Principle 101 UR-URL IdentifierMethod 101.1 UR-URL 100.1.1 UR-URL Real Identifier 100.1.2 XYZT/GTIncept 101.1.3 XYZT/GT Now 101.1.4 XYZT/GT Extension 101.1.5 OtherExtension 101.1.6 Other Address 101.1.7 Other ID Number (ID) 101.2 Name101.2.1 Claimed Identity Name 101.2.2 Real Name 101.2.3 Real Identity101.2.4 Named Identity 101.2.5 Title 101.2.6 Term 101.2.7 OtherDesignation 101.3 Owner 101.3.1 Claim Maker Owner 101.3.2 FunctionalOwner 101.3.3 Maker 101.3.4 Inventor 101.3.5 Discoverer 101.3.6 Parent101.3.7 Legal Agent 101.4. Authority 101.4.1. Official InceptAuthentication 101.4.2 Official Authentication 101.4.3 Official AnytimeAuthentication 101.4.4 Maker Affidavit Authentication 101.4.5 WitnessAffidavit Authentication 101.4.6 Other Legal Authentication 101.5.Keywords 101.5.1 Coordinate Values 101.5.2 Point of Origin 101.5.3Differential Quantity 101.5.4 Latitude 101.5.5 Longitude 101.5.6Elevation 101.5.7 Date/Time 101.5.8 GT 101.5.9 Other Legal Designation101.6 Path 101.6.1 Referential System 101.6.2 Parent System 101.6.3 GPS101.6.4 Geo.Domain 101.6.5 USGS 101.6.6 Metes & Bounds 101.6.7 Others101.7 Profile 101.8 Activity 102 List of Everything 103 Table ofEverything 104 Database of Everything 105 Platform for Everything 106Web Portal of Everything 200 Unitary Infrastructure 200.1 InformationReference Architecture 200.2 Civil Infrastructure 200.3 InformationInfrastructure 200.4 Physical Infrastructure 200.5 ProcessInfrastructure 200.6 Economic Infrastructure 201 Unitary Scope 201.1 AllIdentities 201.2 All Information 201.3 All Objects 201.4 All Systems201.5 All Domains 201.6 All Events 202 Everything Dimensions 203 Layersof Objects 203.1 Event Identities 203.2 Event Information 203.3 EventObjects 203.4 Event System Objects 203.5 Event Sub-System Objects 203.6Object of Everything 203.7 Icebergs of Ideas 203.8 Mountains of Matter204 Levels of Abstraction 204.1 Explication 204.2 Aggregation 204.3Organization 204.4 Synthesis 204.5 Resolution 204.6 Unification 300Unitary Ontology Architecture 300.1 Term.Primitive Entity 300.2Term.Sub-Class 300.3 Term.Type 300.4 Term.Field 300.5 Term.Unity 300.6Term.One 300.7 Term.All 300.8 Term.All In All 301 Unitary Event Ontology301.1 Unitary Top-Level Ontology 301.2 Event 301.2.1 Condition, Objects301.2.2 Condition, Assertions 301.3 Objects 301.3.1 State.Person 301.3.2State.Property 301.4 Assertions 301.4.1 State.Principle 301.4.2State.Transaction 301.5 Person 301.5.1 Class.Real 301.5.2Class.Fictitious 301.6 Property 301.6.1 Class.Real 301.6.2Class.Personal 301.6.3 Class.Intellectual 301.6.4 Class.Public 301.7Principle 301.7.1 Class.Primitive 301.7.2 Class.Law 301.7.3Class.Standard 301.8 Transaction 301.8.1 Class.Claim 301.8.2Class.Function 301.8.3 Class.Action 301.9 Person.Real 301.9.1Sub-Class.Sui Juris 301.9.2 Sub-Class.Non-Sui Juris 301.10Person.Fictitious 301.10.1 Sub-Class.For-Profit 301.10.2Sub-Class.Nonprofit 301.11 Property.Real 301.11.1 Sub-Class.Land301.11.2 Sub-Class.Rights 301.12 Property.Personal 301.12.1Sub-Class.Tangible 301.12.2 Sub-Class.Intangible 301.13Property.Intellectual 301.13.1 Sub-Class.Instrument 301.13.2Sub-Class.Information 301.14 Property.Public 301.14.1Sub-Class.Environment 301.14.2 Sub-Class.Emblem 301.15Principle.Primitive 301.15.1 Sub-Class.Singularity 301.15.2Sub-Class.Force 301.16 Principle.Law 301.16.1 Sub-Class.Theoretical301.16.2 Sub-Class.Statutory 301.17 Principle.Standard 301.17.1Sub-Class.Definition 301.17.2 Sub-Class.Convention 301.18Transaction.Claim 301.18.1 Sub-Class.Statement 301.18.2Sub-Class.Contract 301.19 Transaction.Function 301.19.1Sub-Class.Operation 301.19.2 Sub-Class.Office 301.20 Transaction.Action301.20.1 Sub-Class.Act 301.20.2 Sub-Class.Obligation 302 Relative EventOntology 302.1 Primitive.Position 302.2 Primitive.Point 302.3Primitive.Observer 302.4 Primitive.Specification 302.5 Primitive.Scene302.6 Primitive.Reference-Body 302.7 Event Potential 302.8 Statement ofPrinciple - C1920 Einstein 303 Entity Ontology - C2000 Sowa 303.1Term.Entity ( ) = 

 . 303.2 Term. 

 ( ). 303.3 Term.Independent (I). 303.4 Term.Relative (R). 303.5Term.Mediating (M). 303.6 Term.Physical (P). 303.7 Term.Abstract (A).303.8 Term.Actuality (IP) = Independent∩Physical. 303.9 Term.Form (IA) =Abstract∩Independent. 303.10 Term.Prehension 303.11 Term.Proposition(RA). 303.12 Term.Nexus (MP) = Physical∩Mediating. 303.13 Term.Intention(MA) = Abstract∩Mediating. 303.14 Term.Continuant (C). 303.15Term.Occurrent (O). 303.16 Term.Object (IPC) = Actuality∩Continuant.303.17 Term.Process (IPO) = Actuality∩Occurrent. 303.18 Term.Schema(IAC) = Form∩Continuant. 303.19 Term.Script (IAO) = Form∩Occurrent.303.20 Term.Juncture (RPC) = Prehension∩Continuant. 303.21Term.Participation (RPO) = Prehension∩Occurrent. 303.22 Term.Description(RAC) = Proposition∩Continuant. 303.23 Term.History (RAO) =Proposition∩Occurrent. 303.24 Term.Structure (MPC) = Nexus∩Continuant.303.25 Term.Situation (MPO) = Nexus∩Occurrent. 303.26 Term.Reason (MAC)= Intention∩Continuant. 303.27 Term.Purpose (MAO) = Intention∩Occurrent.303.28 Term.Absurdity (IRMPACO) = ⊥. 303.29 Term.Intermediate Category303.30 Central Category 304 Object Ontology - SUMO Browser C2001 IEEE304.1 SUMO Term Search 304.2 SUMO Term Results 305 Ontology ofOrigination C1875 Eddy 305.1 Term.Principle 305.2 Term.Mind 305.3Term.Soul 305.4 Term.Spirit 305.5 Term.Life 305.6 Term.Truth 305.7Term.Love 305.8 Term.All Knowing 305.9 Term.All Acting 305.10 Term.AllSeeing 305.11 Term.All Being 305.12 Term.All Wise 305.13 Term.All Loving305.14 Term.All Eternal 305.15 Term.All Substance 305.16Term.Intelligence 306 Ontology of Dimension 306.1 I Purpose 306.2 IIValue 306.3 III Concept 306.4 IV Matter 307 Integrated Ontology 308Dimensioned Integrated Ontology 309 Unitary Integrated Ontology 400Unitary RDF Array 400.1 Logic: Has 400.2 Set 400.3 Purpose 400.4 Aspect400.5 Expression 401 Identifier 401.1 Logic.Has UR-URL 401.2 Set.Record401.3 Purpose.Differentiation 401.4 Aspect.Uniqueness 401.5Expression.Address 402 Identity 402.1 Logic.Has Name 402.2 Set.Register402.3 Purpose.Designation 402.4 Aspect.Representation 402.5Expression.Element 403 Origin 403.1 Logic.Has Owner 403.2 Set.Ontology403.3 Purpose.Ownership 403.4 Aspect.Inception 403.5Expression.Condition 404 Agreement 404.1 Logic.Has Authority 404.2Set.Concordance 404.3 Purpose.Instantiation 404.4 Aspect.Legitimacy404.5 Expression.State 405 Constituent 405.1 Logic.Has Keyword 405.2Set.Taxonomy 405.3 Purpose.Classification 405.4 Aspect.Composition 405.5Expression.Category 406 System 406.1 Logic.Has Path 406.2Set.Architecture 406.3 Purpose.Integration 406.4 Aspect.Orientation406.5 Expression.Domain 407 Resource 407.1 LogicHas Profile 407.2Set.Pool 407.3 Purpose.Utilization 407.4 Aspect.Eligibility 407.5Expression.Class 408 Relation 408.1 Logic.Has Activity 408.2 Set.Model408.3 Purpose.Operation 408.4 Aspect.Context 408.5 Expression.Union 409Resource Description Matrix 410 Resource Description Synthesis 411 Logic411.1 Bearer 411.2 Normative Agent 411.3 Condition of Obligation 411.4Obligation 411.5 Sanction 412 ERP 412.1 Work Order/Scope of Work (SOW)412.2 Constraints 413 Analog 414 Sample Records 414.1 Official Record ofOwnership Sample 414.2 Individual Public Claim Record Sample 414.3Vendor Claim Record Sample 414.4 Individual Update Record Sample 414.5Public Directory Record Sample 414.6 Original Incept Record Sample 414.7Government Record Sample 414.8 Personal Record Sample 414.9 PersonalHomepage Record Sample 415 Enterprise Summary Array 415.1 Company Record415.2 Component Record 415.3 Division Record 415.4 Department Record415.5 Work Center Record 415.6 Work Station Record 416 Enterprise DetailArray 416.1 Company Record 416.2 Component Record 416.3 Division Record416.4 Department Record 416.5 Work Center Record 416.6 Work StationRecord 416.7 Resource Record 416.8 Role Record 416.9 Process Record 417Part Number Array 417.1 Part Number - UR-URL 417.2 Part Name - Name417.3 FIG Name - Owner 417.4 View Name - Authority 417.5 Sub-Parts -Keywords 417.6 FIG Number - Path 500 Unitary Processes Architecture500.1 Mint Real Identifier 500.2 Vendor Mint Artificial Identifier 500.3No Authentication 500.4 Authentication By Vendor 500.5 Vendor LayersBlock Authentication Schemas Authentication Products Privacy ProductsSecurity Products Certificates Federations Web Services 500.6 UserID/Password 500.7 Vendor Service Provider 500.8 Vendor Trust Provider500.9 Vendor Anytime Authentication 500.10 Private Ownership Block RealIdentity Real Property Personal Property Tangible Property IntangibleProperty Intellectual Property 500.11 Public Infrastructure OwnershipBlock Public Resources Public Broadband Public “Hot Spots“ Public TVBroadcast Public Radio Broadcast Public Library System Public MailSystem 500.12 Owned Systems Block Computer Monitor CPU StoragePeripherals Software Licenses 500.13 Owned Access Devices Block CellPhone Landline Phone Walkie-Talkie Television Radio Ham Radio BroadbandReceiver GPS Reader Satellite Dish 500.14 Access Vendors Block PhoneCompany Cable Company Wireless Company Cellular Company SatelliteCompany Internet Company Digital Audio Company GPS Company BroadbandCompany Mail Delivery Company 500.15 Access Means Block Phone NumberUser Account Wireless Number Cellular Number User ID Name 500.16 ServiceBlock Service Contracts 500.17 Vendor Infrastructure Ownerhsip BlockTelevision Radio Broadband Telephone Internet Cable Optical FibreCellular Microwave Satellite 500.18 Rented.Proprietary Access DevicesBlock Rented Access Hardware Proprietary Cell Phone Proprietary RFReceiver Proprietary Cable Receiver Proprietary Satellite ReceiverProprietary Broadband Receiver Proprietary Digital Audio ReceiverProprietary GPS Receiver Proprietary Data Receiver Rented IdentityRented Web Software Services Access Rented Web Service Product AccessRented Web ServiceTime Access Rented Web Service Data Storage Access500.19 Access Vendors Block Identity Federations 500.20 Access MeansBlock Federated Identity Vendor Control of Private Identity VendorControl of Private Information Vendor Control of Private Devices VendorBetween Citizen and Govt 500.21 Federated Web Services BlockCommunication Services Authentication Services Privilege ManagementServices Security Services Application Services Directory ServicesHosting Services Search Services Membership Contract End User LicenseAgreement One-Sided Terms and Conditions Hidden Terms and ConditionsPersonalization Content Pre-Screening/Filtering User Profiling and DataMining 500.22 Citizen 500.23 Government 500.24 Middle-Man 501 Forms501.1 Identity Forms 501.2 Unitary Entity Identity Statement 501.3Unitary Event Ownership Statements 501.4 Unitary Event IdentityStatement 502 Tuple Forms 502.1 Tuple Statement 502.2 Unitary TupleStatement 502.3 N-Tuple Statement 502.4 Unitary N-Tuple Statement 503Event Statement Forms 503.1 Unitary Forms 503.2 English Language Forms504 Event Description Forms 504.1 Single Entry 504.2 Multiple Entry 505Programmatic Forms 505.1 Resource Planning 505.2 Operations Sequencing505.3 Binary Pairs 506 Diagrammatic Forms 506.1 Tree Diagram 506.2Critical Path Method Diagram (CPM) 506.3 Cluster Diagram 506.4 MapDiagram 507 Menu Forms 507.1 Prior Art Menus 507.2 Prior Art MenuExpressions 508 Menu Synthesis 508.1 Twelve Programs - 105 Menu Objects508.2 One Platform - 25 Menu Objects 509 Simplified Menu Forms 509.1Program Objects 509.2 Menu Objects 509.3 Navigation Objects 510 ShellWith Simplified Menu Forms 511 Present Invention Owner Self-Mint FlowDiagram 512 Current Embodiment Flow Diagram 513 New Web Services VendorMint Model Flow Diagram 514 Worst Case Future Vendor Mint Model FlowDiagram 515 Owner System Individual Ownership Direct Access 516 RenterSystem-Vendor Ownership-Vendor Control 600 Unitary Apparatus 600.1 COTSor Open Source Computer System 600.2 Event Data 600.3 Navigation BarWith Links 600.4 Shell 600.5 COTS or Open Source Spreadsheet SoftwareWith Search and Hyperlinks 600.6 COTS or Open Source Database Software600.7 COTS or Open Source Shell Software With Simple Tools 600.8 COTS orOpen Source Predicate Logic Software 600.9 COTS or Open Source Web PageSoftware 600.10 COTS or Open Source Browser Software 600.11 TabularArchitecture Rows and Columns 600.12 Infinite Integration With UR-URLIdentifier Method Scope 600.13 Infinite Range With Infinite UR-URLIdentifier Method Scope 600.14 Finite Integration With Finite IdentifierMethod Scope 600.15 Variable Relational Tables 600.16 Finite Range WithFinite Identifier Method Scope 600.17 Variable Columns 600.18 FramesWith and Without Content 600.19 Access 601 Unitary Shell 600.20 CommonArchitectures 600.21 Vendor Ownership Web 600.22 Private Ownership Web600.23 Website, Search Engine, and Directory of Everything in the PublicDomain 600.24 Information Systems 700 Computing Module 703 Bus 704Processor 708 Memory 710 Storage Devices 712 Media Drive 714 Media 720Storage Unit !/F 722 Storage Unit 724 COMM I/F 728 Channel 740 LabelingProcess 740.1 Unlabeled Event 740.2 Receive Unlabeled Event 740.3Non-Transitory Computer Executable Code 740.4 Label Event 740.5 SelectLabel 740.6 Which Label 740.7 Assign Label to Event 740.8 Store LabeledEvent 740.9 Non-Transitory Computer Storage Medium 750 Sample LabeledClaims 750.1 Claims to Ownership of the Event of “Rock Concert” 750.2Claims to Ownership of the Event of “Sky” 750.3 Claims to Ownership ofthe Event of “Human Thinking” 750.4 Claims to Ownership of the Event of“God” 750.5 Claims to Ownership of the Event of “Fortune Telling” 750.6Claims to Ownership of the Event of “Tarot Website” 760 UnitaryTechnology

DETAILED DESCRIPTION OF THE INVENTION

Overview

It isn't immediately obvious how an inventory control database and humanresources database could have the same information structure as thefinancial transaction database and the document knowledge base. At theobjective level these resources seem to be very different with widelydiffering properties and applications. But in abstraction everything inan information system—every file, every folder, every document, everyrecord, every activity, every system, every object—every asset—is anevent that can be listed and directorized with eight universal terms ofdescription common to all resources (FIG. 34). Integration andinteroperability, both internally and with clients and partners, dependson such correspondence in data structures and formats. The definingcriterion is ownership, the cohering basis is incept identity, andUR-URL relative referential geotemporal coordinates are universalresource identifiers for all users and all uses. Identity is theplatform.

The same architecture works for personal and civic systems too, but withsix terms (FIG. 33). Value and distinction lie in breadth of publicscope, not depth of private detail. The resultant directory looks like abig phone-book-like list of links to everything everyone needs to findin a simple table that everyone knows how to use. What you want is whatyou get

Unitary Event Information Architecture

TABLE 6 Unitary Terms of Description ARRAY IDENTIFIER IDENTITY ORIGINAGREEMENT CONSTITUENT SYSTEM RESOURCE RELATION EXPRESSION AddressElement Condition State Category Domain Class Union ASPECT UniquenessRepresentation Inception Legitimacy Composition Orientation EligibilityContext PURPOSE Differentiation Designation Ownership InstantiationClassification Integration Utilization Operation SET Record RegisterOntology Concordance Taxonomy Architecture Pool Model LOGIC ∩ UR-URL ∩Name ∩ Owner ∩ Authority ∩ Keyword ∩ Path ∩ Profile ∩ Activity Note:Table 6 data is represented in FIG. 31 Matrix of Ontological TermsOverall Structure and Function

Items 200.1-6 comprise components of a global network of informationcommunication systems. The components of the present invention areidentified as sub-components of Unitary Technology, the name thatexpresses the universal utility of the main embodiment, UnitaryReference Architecture 100. Further sub-components 101 through 106comprise alternate functional embodiments that extend utility.Infrastructure Components are illustrated in FIG. 6.

Unitary System Components

-   -   200.6 Economic Infrastructure: Principles of economics, exchange        systems, metrics, markets, financials, communication systems,        the Internet, the telephone system, media, devices, hardware and        software    -   200.5 Process Infrastructure: Business methodologies, production        systems, delivery systems, supply chain networks, media,        devices, hardware and software.    -   200.4 Physical Infrastructure: All people, all property; all        places, ideas, artifacts, objects, assertions; everything.    -   200.3 Information Infrastructure: Language, classification,        representation, media, devices, hardware and software.    -   200.2 Civil Infrastructure: Principles of democracy,        self-representation, ownership, rules, values, norms.    -   200.1 Information Architecture: Unitary Reference Architecture        Universal Resource Identifier (URI)        -   100 Unitary Reference Architecture—URA Self-service single            sign-on identity for all users and all uses.        -   101 Event Identity Model—Unitary Identity Architecture            (UR-URL Identifier Method)        -   102 Event Information Model—Unitary Event System (List of            Everything)        -   103 Event Object Model—Unitary Event Field Modeling Method            (Table of Everything)        -   104 Event System Model—Unitary Event Integration and Network            Architecture (Database of Everything)        -   105 Event Process Model—Unitary Event Programming (Platform            for Everything)        -   106 Unitary Event Model—(Web Portal to Everything)

Taken in aggregation, this high-level list of components is intended torepresent the full spectrum of scientific principles and technologycurrently governing the interpretation and application of identity asessential information architecture. Each domain of systems uses identityfor varying purposes and applications. Systems within each domain havedifferent architectures. There's overlap, but more difference thancommonality in the numbering schemas. URA unifies all schemas andpurposes with one method.

Example of Unitary Identity Applied

-   One Entity>Many Claims-   One Claim>Many Entities

Let's imagine a unitary system contains all the public property recordsfor Podunk County. You want to use the system to find a house to buy.You go to the search utility, enter the location coordinates for theneighborhood in question, and the search results screen pops up. Itlists all the houses by street and owner, either way, or by keywords inthe description. Each home may have more than one listing, more than onedatabase address primary URA ID key (UR-URL).

The county property records will all be owned by, and show as the maker,PDC. The link to more information directs the browser to the PDChomepage. The primary key for each property would have as the URA anXYZT that has the latitude, longitude and elevation as the first threesets of code variables, and then the date and time of sale as the lastset. Because this is an official public record, the format for thedigits might be fixed; a “standard” for all addresses would probably usethe US Geological Survey (USGS) system. This URA and record might looklike:

-   -   THE OFFICIAL RECORD OF OWNERSHIP SAMPLE—FIG. 66        -   UR-URL N02649095.W08006333.E00040.10172000.133000        -   Name Record of single-family home ownership        -   Owner PoDunk County Tax-Collector        -   Authority Deed or Title Company; Has artifact        -   Keywords Instantiation Incept date/time/loc at closing; Has            desc        -   Path Web: pdc.fl.gov/records/titles

The owner might also register the property in preparation for sellingit. They want to be known as the owner, they want to be visible andlocatable. So they register. The ID would be the same, because URA coulduse the standard format for the event object house. This is what wouldbe same/different:

-   -   INDIVIDUAL PUBLIC CLAIM SAMPLE—FIG. 67        -   UR-URL N02649095.W08006333.E00040.10172000.133000        -   Name N02649095.W08006333.E00040.10172000.133000        -   Owner Public, John Q. and Public, Jane Q.        -   Authority Web: pdc.fl.gov/records/titles        -   Keywords Claim: Incept date/time/loc at closing; Has title,            Joint        -   Path Web: jqpfamily/homepage

The real estate company might also register the same house on acommercial site. They don't want people to know who owns the house orwhere it is. They want the users to come to them. Their record wouldhave a totally different initial URA based not on the piece of property,but based on the Real Estate Company's URA. They would not beregistering the house as property, because they don't own it. They'reregistering the listing. The listing is their property and resides attheir location in a file folder in the file room. The listing would looklike this:

-   -   VENDOR'S CLAIM SAMPLE—FIG. 68        -   UR-URL S12345675.W22222333.E00050.04012003.108300        -   Name Listing for single-family home        -   Owner Good Realty Company Inc        -   Authority Listing 3333-456        -   Keywords Fl pool home; gated community; water view; 3% to            selling broker; 3br; 2ba; FR; Bonus rm; 3CGrg; owner will            carry 2nd        -   Path Web: goodrealty.com/listings/homes/florida.htm

Part of the contract with the realtor might stipulate that John add therealtor's link to his own registration record, or he would maybe set aflag in his mailbox that “read” the email and if it matched the keywords“house” “for sale,” the email would go automatically (redirected) to therealtor and not John. Realtors don't like it when owners snag buyersdirectly. So John would go to the site, click on “Update record” and addthe realtor's http to the LINK field. Now, John's personal record wouldlook like:

-   -   INDIVIDUAL UPDATE RECORD SAMPLE—FIG. 69        -   UR-URL N02649095.W08006333.E00040.04012003.108300 (? T)        -   Name N02649095.W08006333.E00040.10172000.133000        -   Owner Public, John Q.        -   Authority Web: pdc.fl.gov/records/titles        -   Keywords Now date/time/loc at record registration; Has            agent, Good Realty        -   Path Web: goodrealty.com/listings/homes/florida.htm

Finally, the telephone company may also assign a URA “phone number” forthe house. ATT “owns” the phone numbers now, they are the mint. Theyissue identifiers—phone numbers. Their method of formatting GPS signalsmight use an abbreviated system that's easier for users to remember.Instead of the whole standard longitude, they might use an alternatesystem like Geo Domain. It generalizes regions, like area codes, butthey make sense to the location relative to the basic “standard.”Imagine date formats, you can use Apr. 2, 2002 or 02APR02 and they meanthe same thing, they're just different formats. And you can change theformat at a click, convert. This means they are the same but different.This one uses: “minutes.degrees.tendegrees.geo.”

Also, if it's a device, it may be fixed or mobile. The time signature isa constant string of location signals that correspond to where thedevice is. Technically, every minute (or billing increment) is atransaction at certain location. Transactions are grouped into units of“calls” between locations and numbers. So the phone company's internaldatabase and directory record might look like this, if they used the GeoDomain method as an alternat referential ID format:

-   -   PUBLIC DIRECTORY RECORD SAMPLE—FIG. 70        -   UR-URL            2e33n.5e5n.2e10n.37e47n.1e5n.10e20n.E00040.10172000.133000        -   Name John Q. Public        -   Owner Phone Co        -   Authority Web: pdc.fl.gov/records/titles (which references            maker and location)        -   Keywords Web: jqpfamily.com/communication/access;            Constraint, No solicitation        -   Path Web: phoneco.com (where this record is)

John Smith was originally registered as a dependent citizen entity atthe time of his birth, which was witnessed by the hospital andauthenticated by the local governmental agency that maintains vitalstatistics. His incept record would include standard information:

-   -   ORIGINAL INCEPT CLAIM SAMPLE—FIG. 71        -   UR-URL S00236666.E55555555.E00010.08011951.233022        -   Name NameFirst, John, NameMiddle, Q., NameLast, Public        -   Owner Makers, Mary Q. Public nee Smith and Jack Q. Public        -   Authority Witness, Web: goodhospital.com/records/contact.htm        -   Keywords InceptLoc, S00236666.E55555555.E00010; Incept D/T            0.08011951.233022        -   Path Web: pdc.fl.gov/deptvitalstatistics/ (where the            authenticating artifact is)

John Smith is an “object” in the USGOV system. This could be hispersonal URA for everything, if he wants. It's linked to a county orhospital registration of live birth or personal affidavit that“authenticates” his existence. The rest of the government's internaldatabase fields can be anything, but this would be the public recorddisplayed. It simply acknowledges that John Smith is a person with aname and a link. It is the URA for everything official.

This is not a system anyone can see or get into. It is the USGOV and itis behind firewalls. The public part of the public record is the nameand URA ID. The USGOV records and other regional public entities arealso registered and listed in the pubic domain with the following kindof entry:

-   -   US CENSUS RECORD SAMPLE—FIG. 72        -   UR-URL S00236666.E55555555.E00010.08011951.233022        -   Name John Q. Public        -   Owner US Census Bureau        -   Authority Web: pdc.fl.gov/deptvitalstatistics/ (where the            authenticating artifact is)        -   Keywords Has (name, relation, gender, DOB, Latino Y/N, race)        -   Path Web: us.gov/census/ (where this record is)

John Smith can also register himself, and this main person entry is whathe chooses to reveal to the world. The URA is public. The informationassociated with it is limited to what the maker wants to put in thepublic record. Most people like to be in the phone book. They want to befound. Registering your self as an entity is a prerequisite toregistering your property, but ATT can register your phone number andname as part of a whole phone book of people's phone numbers and namesbecause they “own” the mint and information in it. Users can requestexclusion, just like with regular user-owned personal data today.

-   -   PERSONAL RECORD SAMPLE—FIG. 73    -   UR-URL N02649095.W08006333.E00040.10172000.133000 (chooses home        UR-URL)        -   Name John Q. Public        -   Owner John Q. Public        -   Authority Affidavit        -   Keywords No solicitation        -   Path None

Or John Smith might want to be found, so he might add to his record“Link” the device ID-phone number, or his homepage, or his business,whatever he wants. But just because the link is there and people canfind his homepage, does not mean they can get into his personal privatedata behind that homepage. It might just have a “log on” screen forfamily members to see the photo's page, or a “sign-up here if you wantme to receive your email” where he makes the people give HIM informationbefore he'll accept the email. Whatever, this page is what he wants theworld to see and know about him. His listing in might look like this:

-   -   PERSONAL HOMEPAGE RECORD SAMPLE—FIG. 74    -   UR-URL N02649095.W08006333.E00040.10172000.133000 (chooses home        UR-URL)        -   Name John Q. Public Homepage        -   Owner John Q. Public        -   Authority Affidavit        -   Keywords PMP, CPF, project management; Resume:            jqpfamily.com/resume.htm        -   Path Voice/data Web: jqpfamily.com/communication/access (his            routing program)    -   SEARCH RESULTS SAMPLE—FIG. 75        -   If someone wanted to find John Smith's phone number, they            could search on the name John Smith and the following            results would be displayed:            -   Search: John Q.Public            -   UR-URL N02649095.W08006333.E00040.10172000.133000            -   Homepage: Web: jqpfamily.com/login.htm            -   Phone Co: Web: phoneco.com/jqpfamily.com/login.htm            -   PDCFL: Web: pdc.fl.gov/records/titles.index.htm        -   Search 123 Palmy Way, City of Warmtown, County of Po Dunk            -   UR-URL N02649095.W08006333.E00040.10172000.133000            -   PDCFL Web: pdc.fl.gov/records/titles.index.htm            -   Owner Web: jqpfamily.com/login.htm            -   Agent Web: goodrealty.com/listings/homes/florida.htm

The beauty of a semantic web such as this is it anticipates the messynaturally evolving cross-referenced linkages across and betweenentities, domains, contexts, and applications around the world and inthe universe at large. All exist harmoniously side-by-side in URA. Ateach location, unless you have the password and authorization to get in,you can't find out anything except his name and the URA number and thefact that he is listed as an element in each of these proprietarydatabases. If it is the ATT site, it would go right to the phone numberURA and it would be displayed or say Unpublished, just like a paperphone book. If you went to the IRS site, it would not even let yousearch. If you go to county records homepage, you can search on name orURA of the property or the owner and get one record, the record you'relooking for.

If they go to the realty website, there is only information about thehouse and the phone number of the real estate agent. If the searcherreally wanted to, just like today, they could go to the county recordsand find the house, then go to the ATT site to find the phone number, orto the owner's site and find them or their agent. The point is toautomate a public system, not make private systems public.

Information Architecture

An existing upgrade proposal for web infrastructure is the addressingmethod Geo Domain, which stipulates use of DNS to encodelatitude/longitude for any element in a hierarchical n-tree. This is analternate to the lon/lat architecture we use for navigation, and it hasa different way of dividing up the grid: Geo.Domain Method:₂₅

Minutes.Degrees.Tendegrees.Geo, e.g, 37e47n.1e5n.10e20n.geo

Digital Earth and W3C suggest identification using geographicalcoordinates in an abbreviated format. Unitary Technology is capable ofaccommodating this and all GPS formats. It is anticipated thatultimately one standard format will be adopted worldwide for telephony,and this one seems to have the most flexibility.

The examples shown are not intended to specify formats or specific codevariations for particular applications. Rather, they seek to illustratethe flexibility with which individuals can manage the way informationabout them is represented in the systems of those they chose to dobusiness with.

Operation—Main Embodiment

Ordinary Everyday Person

The present invention assumes current technology as would be known to aneveryday person of reasonable intelligence and education that has alibrary card, computer, surfs the web, and watches the DiscoveryChannel. Unitary Reference Architecture is fundamental technology. It'sbig but simple.

URA is an combination identity-identifier-addressing-indexing businessmethod for information system integration and control, and is notdependent on medium, just like “information” isn't. It's harder to dothis manually, even though you can. An ordinary everyday person wouldbuy a personal computer, big or small, doesn't matter, and select anoperating architecture—such as one that's cheap or free like Unix orLinux, but Windows and Mac are OK too.

Common off the shelf components are assumed, so, it's reasonable tofurther assume no special understanding of computers or programming isnecessary. The ordinary everyday person may know a little, or a lot, butwhenever they hit a point where they need help, they get it, or hire aprofessional. Assumption of prior art functionality is captured inglobal terms and common narrative both for simplicity and because thepresent invention really is that simple. The way you do anything better,if it has to do with identity, is to take its old system of identifierswith limited intent, less capacity, and no universality, and instead useUnitary Reference Architecture and get unlimited unitary integrationinteroperability opportunities.

How to Make a Semantic Model of Everything Recorded

1. Reference Architecture

Take a piece of paper and draw six columns. Leave the first columnblank.

2. Identity—Name—Point

In the second column, list all the things you know about. That's all thepeople, all the places, all the stuff, and all the ideas. It doesn'tmatter if you get everything the first time, you can add more later. Youhave to do that anyway, as new stuff happens. For now, just list all thenames of individual things you can think of. Identity means what it is,its name.

3. Origin—Owner—Observer

In the third column, put the name of the person who owns each thing.Everything has an owner. People own themselves. Event ownership is whatrepresentation is all about. If it's a mountain or something you're notsure about, the country where it is probably owns it. Put them on thelist. You can list great ideas using the inventors or discoverers as theowners. Everything known can be listed as an event. Even stuff thathappens is owned by the people there. There would be lots of owners forthe event “Super-Bowl.” You might want to have just “Super-BowlBroadcast” which is probably owned by the television network. Same thingwith stuff. For your first version, you should probably have a few bigmountains rather than a million little molehills. Just a suggestion.It's still a Model of Everything, just bigger clumps. You can break outthe detail later.

4. Agreement—Authority—Specification

In the fourth column, put the name of the instrument or agency thatcorroborates ownership. Just because someone claims ownership doesn'tmake it so. This could be a deed, or birth certificate, or contract, orthe Department of Vital Statistics, or county that maintains propertyrecords.

5. Constituents—Keywords—Scene

In the fifth column, put some keywords and phrases that describe thething. If you want, you can just copy other lists of things likedictionaries and atlases. If you're using a computer, you can load thewords in the second column in the first place. Saves a lot of timelisting basics.

Also in this column, if it's a thing, put the address where it is. Ifit's a person, put the address where s/he was born, and the date andtime they were born (or, the date and time the thing was bought, ormade, or began or was discovered)

6. System—Path—Reference-Body

In the sixth column, put the path or address of each thing's governingsystem, the system it's in—the source of applicable standards andprotocols.

7. Identifier—UR-URL—Position

Now we get to the part where it's particularly helpful if your list isin a spreadsheet or relational database. You can do this manually, butit will take longer. Your list is probably pretty big. Look at a map oruse a hand-held GPS navigation tool to find the locational coordinatesthat match the physical addresses in column five. You could do this partfaster with software package, probably inexpensively. Put thesecoordinates in the first column, and put the name of the GPS system incolumn six. Then, convert the incept dates and times to number-strings,and put those new numbers at the tail end of the first numbers in thefirst column. Even though today's GPS isn't exact to millimeters, itdoesn't matter. All you need is one exact reference. Everything else isan offset. Use a measuring tape if you have to.

This is the identity address, or “identifier” or ID—the UR-URL. This isimportant. People and things have real incept identity. The realidentity address is used as the UR-URL identifier. Just don't call thesenumbers identity. They are identifiers. It's a legal thing. Allidentifiers in a system must be unique, and these are. We're using thereal Unitary Reference Architecture as our database referencearchitecture. We all know the math, so uniqueness is naturallymaintained without central mints.

Once we have UR-URLs for everything, we can do anything. Like make morelists of stuff in groups. But we can also do a whole lot more.

8. Cross-References

Compare all the stuff's keywords in column five, and every time there'sa match, put the UR-URL from column one of the thing that matches intothe Keyword column. This will be lots of cross-references. The universegets pretty messy after a while. So do databases. If the Keyword columngets too full, you can group them into some other columns.

9. Ontology

If you have a classification system, you can use that with the keywordsto organize stuff according to things like science or public records orthings that are red. Whatever. But the organizing only comes whensomeone wants to find something specific. The rest of the time, this isjust a list and the basic order in its raw form is location, based onthe number order of the UR-URLs.

10. Universality

If you want, you can put in some other columns, like maybe the codestring that makes an elemental image or unitary waveform of the thing,but that would only be needed if you wanted to replicate it. That's notsomething you're probably going to do, so these few columns are prettymuch all you need for a basic Model of Everything. You have all thestuff and all the people, and where there is ownership, a cross-linkbetween their identifiers.

This is a Semantic Model of Everything Recorded. The referencearchitecture is the network. If anything new happens, it already hasidentity ready and waiting. Just use the identities as identifiers andadd them in.

11. Product

It's really just a big Model of Everything and who owns it and where itis, cross-referenced to everything else—one set of event identities inone system that's already real, already verifiable, already a matter ofpublic record. The thing that's new is who owns and controls access tothe information. Here, like in life, makers do. Self-service identitymakes digital self-representation possible.

How to Make a New Net with New Network Information Architecture

(1) Construct a model of |everything| (1000) by creating a unique ur-urlreal identity-identifier for each event according to the steps

-   -   a) claim ownership of a real event as is common everyday        practice in the public domain    -   b) identify the real event by name and/or symbols    -   c) claim a real address of said real event    -   d) claim a real event incept time of said real event    -   e) relate term symbol “t” to “time” as is everyday practice    -   f) relate the real event incept time value to symbol “t”    -   g) select any standard referential system and set of referential        protocols from numerous standard referential systems commonly        used with mathematical constructs and/or georeferencing        applications    -   h) relate term symbols “x”, “y”, and “z” to three dimensional        vector coordinates as is everyday practice    -   i) relate coordinate terms “x”, “y”, and “z” with terms        “latitude”, “longitude”, and “elevation” respectively, as is        everyday practice    -   j) apply selected standard protocols to determine real        three-dimensional vector coordinate values of the real event        address    -   k) associate said real event address values with real        three-dimensional “xyz” vector coordinates corresponding to said        real event address    -   l) concatenate values “x” and “y” and “z” and “t” corresponding        to said real event address, resultant “xyzt” combination        comprising the unique ur-url real identity-identifier, and    -   m) assign said unique ur-url real identity-identifier to said        real event    -   n) claim relation of said unique ur-url real identity-identifier        to said real event as is common in everyday identity        instantiation practice in the public domain    -   o) secure official authentication as is common everyday practice    -   p) publish claim to ownership of event identity as is common        everyday practice    -   q) repeat steps (a) through (q) for each event in all events.

(2) Construct a zero-dimensional model of |everything| (101) comprisingconstructing table apparatus with tabular architecture, column and rows,and making one column, and making an infinitely extensible number ofrows, and cohering the infinitely extensible number of rows with onesystem of said unique ur-url real identity-identifiers according to themethod and steps of (1), and placing one unique ur-url realidentity-identifier for each event in all events, one per row in columnone, such that each point of zero-dimension event potentiality inspacetime is represented by the particular ur-url with which itcoincides.

(3) Construct a one-dimensional model of |everything| (102) according tothe steps according to (2) with the addition of a second elementcomprising constructing a zero-dimensional model of |everything|according to the method and steps of (2), and making a second column,and listing in the second column names which represent identity of eachreal event claimed according to the method and steps of (1), and placingnames one per row in correspondence with the particular ur-url realidentity-identifier with which its claimed real address coincides, andcontinuing until each real named event is associated with the particularur-url real identity-identifier with which it coincides according to themethod and steps of (1).

(4) Construct a two-dimensional model of |everything| (103) according tothe steps according to (3) with the addition of steps comprisingemploying commercial off the shelf or open source computer system, andusing commercial off the shelf or open source spreadsheet software withsearch and hyperlink functionality, and making a one-dimensional modelof everything according to the method and steps of (3) and addingcolumns, and assigning to additional columns, beyond ur-url column andname column, column field labels selected from the group consisting ofowner, authority, keyword, path, profile, activity, and classifyingnamed event properties with ontology terms, and describing named eventsby inserting particular values and properties in row cells correspondingto field labels for each named event, and creating hyperlinks betweeninstances of particular events according to common everyday spreadsheetusage, and continuing until each named event is classified and/ordescribed.

(5) Construct a three-dimensional model of |everything| (104) comprisingthe steps according to (4) with the addition of steps comprisingemploying commercial off the shelf or open source database software, andmaking a two-dimensional model of everything according to the method andsteps of (4) and adding relational tables, and updating original realevent records with new real-time event data, and using original claimedincept real xyz for each updated event, and using real event updateactivity real time as value related to “t”, and concatenating new xyztreal event real identity-identifier ur-url, and assigning the new xyztreal event real identity-identifier ur-url to real event updateactivities in corresponding relational tables, and integrating any andall relational tables that share same ur-url real identity-identifierterms.

(6) Construct a four-dimensional model of |everything| (105) comprisingthe steps according to (5) with the addition of steps comprisingemploying commercial off the shelf or open source shell software withsimple tools, and employing commercial off the shelf or open sourcepredicate logic software, and making a three-dimensional model accordingto the method and steps of (5) containing said named real eventsrelating to original event term identities defined according to themethod and steps of (1) and which identities were related to all otherreal event identities according to the method and steps of (2) and whichwere listed by said real identity name and said real ur-url realidentity-identifier according to the method and steps of (3) and whichwere described and classified according to the method and steps of (4),and which were associated in relational tables according to the methodand steps of (5), and employing said ur-url real identity-identifiers asrelation variables in standard programmatic forms, and creatingprogrammatic sentences by specifying “words” of consisting of saidur-url real identity-identifiers that refer to and invoke by hotlinkoriginal terms and definitions contained in corresponding real eventrecords, and creating sentences in english or any language by specifyingsaid ur-url real identity-identifiers that refer to and invoke byhotlink original english or other language terms and definitions incorresponding real event records, and drawing pictures with “palettes”of said ur-url real identifiers that refer to and invoke by hotlinkoriginal programmatic objects contained in corresponding real eventrecords, and assigning said ur-url real identity-identifiers to realhard drive and operating system event addresses, and creating activityschedules by linking real named event's predecessor and successor ur-urlreal identity-identifiers.

(7) Construct an all-dimensional model of |everything| (106) comprisingthe steps according to (6) with the addition of steps comprisingemploying commercial off the shelf or open source web page software withsimple tools, and employing commercial off the shelf or open sourcebrowser software, and applying laws, rules, norms, conventions, andlegal requirements corresponding to everyday analog institutions andinstantiation processes, and making a four-dimensional model accordingto the method and steps of (6), and employing simple web page softwareto create website page text and graphics, and employing simple browsersoftware to access website page text and graphics, and recording ownedproperty and identity ownership claims according to the method and stepsof (1) for instantiating new real event identity, and operating a webportal front end to deliver access to everything by everyone, andemploying said ur-url real identity-identifiers in place of telephonecommunication identity addresses, and at the same time using said ur-urlreal identity-identifiers in place of internet identity-identifiers,domain addresses, and internet protocol addresses, and at the same timeemploying said ur-url real identity-identifiers in place of vendoraccount identity-identifiers, and at the same time employing said ur-urlreal identity-identifiers for official governance and participationprocess identity-identifiers owned by private citizens, and at the sametime employing said ur-url real identity-identifiers in any and allcapacities and instances where identity-identifiers are employed, andachieving universal interoperability by means of shared said system ofsaid ur-url real identity-identifiers applied in constructs of zero toall dimensional product versions of the present invention.

How to Make an Operating System Information Architecture

-   1. Take a computer off the shelf-   2. And some C++, or any semantic specification tool-   3. Add URA-   4. Assign identifiers to operating instructions the same way you do    now-   5. Assign identifiers to memory storage medium the same way you do    now-   6. Assign identifiers to data events the same way you do now, but    use unitary event identifiers instead of other identifier methods,    for everything in the whole system

By using the same system of identifiers you use for event objectidentifiers also for memory address identifiers, you could eliminate onewhole extra term—probably not as much as a thirty percent overallreduction in memory, but every byte counts. In the old computerinformation architecture, if you use real physical location, all theidentifiers would always be unique, but they'd change every time youperformed routine disk maintenance. You could maybe add a rule in theold reference architecture that kept track all the changes, but usuallythere's just another identifier. This way you always know what and whereeverything is.

But if your operating system information architecture uses the same URAreferential method, code syntax, and nomenclature as the system of URAevent objects, then the principle of symmetry would be invoked to themax. At its most primitive level, the system identifier is the objectidentifier is the object identity when object identifier used is itsreal microscopic location address in the computer. Now you haveoperating system information architecture.

How to Make an Event Oriented Programming Language

-   1. Take a box of Object Oriented Programming, and a box of Model    Driven Architecture-   2. Make a Model of Everything with the system identity: Event Object    Oriented Programming-   3. Construct programmatic instructional sequences by making    mini-lists of executable identifiers.

Object Oriented Programming automates programming by clumping frequentlyused lists of instructions that do frequently needed operations into onereusable functional template or “object.” Single operation objects canbe connected to other objects to make bigger objects. A program is abunch of objects in a certain order. Model Driven Architecture meansbigger clumps for more functionality at higher and broader levels. Eventobject orientation is the next higher level of combination, followed bysystem event object, and unitary object. URA completes the objectorientation evolution. Everything's a system object—an operation is anevent object, a process is an event object, resources are event objects,terms and protocols—all event objects in one system.

Unitary Reference Architecture provides one unitary system ofidentifiers for all event objects. Writing a program is as simple aslinking identifiers when the object and its identity and its locationand it's assertion of utility are all referentially embedded in theunique identifier primary key code. Real referential geo-temporalmathematical coordinates are conveniently grouped and inherentlyindexed. The time vector provides a handy way to assign duration andsequence. Event identity inheres force and field, process and content,object and assertion and it describes, locates, differentiates,integrates, orders, directs, routes, and controls. Unitary programmingtools and techniques also apply as method and means for simulation,replication, synthesis, and molecular models of systems of all sizes andcomplexities. A Model of Everything provides a larger construct formodeling event phenomena in whole-systems contexts.

Nanotechnology.

Reference architecture for a Model of Everything includes very smallthings too. The key aspect that makes this model not just bigger butdramatically different from the many partial models and modelingtechniques used today is the fact that, with URA, event objects andevent assertions share the same identity, and same identifier. Thisprinciple of symmetry between analog identity and digital identifier isespecially useful in controlling nano-processes.

Broadly speaking, agents (miniature machine agents, biological agents,information agents) are controlled by software programs that consist ofidentified lines of code that first define the field and then establishthe terms of relationship and interaction. Then, transactionalinstructions are applied to produce desired results. A typicaltransaction would consist of an identifier, an object name ordescription, and an operation, which itself consists of a process stepand sequence or time. An operation might be as simple as “move objectfrom one place to another in the system,” or as complex as a group ofsoftware or machine compound objects that execute additional operationswith other objects in the system.

A Unitary simulation would similarly define the field and establishterms of relationship and interaction. Once all points are addressed,the whole set of operating instructions would consist of a series ofobject addresses alone, where the address is XYZT/gt and applies to boththe point and the object that occupies it along it's path ofinteraction. Thus, the object and the place where it's supposed to be aswell as the time it's supposed to be there are all in the identifier.This is about as efficient as code gets. It concurrently leveragessignaling technology by using real identity addresses as communicationidentifiers, plus models can be easily linked and merged withoutquantity constraints imposed by standard addressing methods. With hugequantities of nano-objects, every character counts. Inherentextensibility facilitates aggregation of subsections which may beconstructed independently and assembled modularly.

Alternate Embodiments

Grid Computing

Unlimited grid addresses. Unlimited relative grid addresses.

Blade Technology

IBM Blade technology specifies a “fabric” of I/O addresses; URA providesfabric grid addresses, and a method of referential relative addresses.

Virtual Storage Solutions

Virtual storage theory links data stored in non-contiguous physicallocations and simulates unitary configuration through address/ID codestructure nomenclature. URAs addresses provide system unification at theidentity level, making physical location constraints not onlytransparent but also meaningless. What coheres a system is its primarykey identity definition.

Wireless Communication

In the future, mobile communication from multiple devices will connectmore of us, where hard-wired infrastructure now predominates. URAprovides identity for the caller, for the device, and for thetransaction, thereby extending mobile wireless data capabilities fortransaction management. Furthermore, URA provides a multiple-optionschema for alternate telephone numbers themselves.

Short Message Systems

Theoretically, anyone could set up a COM business/phone company usingtheir own URA identity addresses as phone numbers. This is more likelyin the smaller domain of messaging; however, alternate national andglobal systems could be established.

Bar Code Adhesive Strips

With URA, individuals as well as corporations can easily track theirproperty items with mini-lo-jack strips. Examples: personal homeinventory, children, eyeglasses, pets, anything that gets lost, slap asticky-back beeping strip with programmable address options that signalsdirectly to the main system exactly where each and every item may befound. When the “thing” is children (“jewelry” or “accessory” tags), anational public record domain becomes a vital resource.

Governance, Secure “Public ID” Structure

URA is the only national ID schema that applies universally to allcitizens of the world. It contains only demographically neutralinformation about claims to ownership specified voluntarily by makers.

Artificial Intelligence

Memory is just a stored event description. URA integrates complexsystems of assertions as easily as objects. The identifier'stime/location simplifies both linear and non-linear dynamics ofconceptual relationship.

Miscellaneous Representational Whole-System Applications

Genetic Simulation/DNA Modeling Platform; Knowledge Base Management;Traffic Control; Directories/Registries, Inventory Systems; EmergencyHealthcare Profiles, Cameras that capture grid addresses as real-timeaddress identifiers with meta data.

Alternate Referential Addressing Method Embodiment

As an alternate embodiment and addressing schema for assigningreferential addresses associated with a single entity or event address,UR-URL uses a modified Sierpinski carpet algorithm. In this embodiment,individual unique ID's are assigned relative to an original unique ID,in a manner that corresponds to the standard “make hole” method,starting with a square, dividing it into a 3-by-3 grid, and removing thecenter square; then repeating the process for each remaining square.₂₇

Referring now to FIG. 111, computing module 700 may represent, forexample, computing or processing capabilities found within desktop,laptop and notebook computers; hand-held computing devices (PDA's, smartphones, cell phones, palmtops, etc.); mainframes, supercomputers,workstations or servers; or any other type of special-purpose orgeneral-purpose computing devices as may be desirable or appropriate fora given application or environment. Computing module 700 might alsorepresent computing capabilities embedded within or otherwise availableto a given device. For example, a computing module might be found inother electronic devices such as, for example, digital cameras,navigation systems, cellular telephones, portable computing devices,modems, routers, WAPs, terminals and other electronic devices that mightinclude some form of processing capability.

Computing module 700 might include, for example, one or more processors,controllers, control modules, or other processing devices, such as aprocessor 704. Processor 704 might be implemented using ageneral-purpose or special-purpose processing engine such as, forexample, a microprocessor, controller, or other control logic. In theillustrated example, processor 704 is connected to a bus 703, althoughany communication medium can be used to facilitate interaction withother components of computing module 700 or to communicate externally.

Computing module 700 might also include one or more memory modules,simply referred to herein as main memory 708. For example, preferablyrandom access memory (RAM) or other dynamic memory, might be used forstoring information and instructions to be executed by processor 704.Main memory 708 might also be used for storing temporary variables orother intermediate information during execution of instructions to beexecuted by processor 704. Computing module 700 might likewise include aread only memory (“ROM”) or other static storage device coupled to bus703 for storing static information and instructions for processor 704.

The computing module 700 might also include one or more various forms ofinformation storage mechanism 710, which might include, for example, amedia drive 712 and a storage unit interface 720. The media drive 712might include a drive or other mechanism to support fixed or removablestorage media 714. For example, a hard disk drive, a floppy disk drive,a magnetic tape drive, an optical disk drive, a CD, DVD or Blu-ray drive(R or RW), or other removable or fixed media drive might be provided.Accordingly, storage media 714 might include, for example, a hard disk,a floppy disk, magnetic tape, cartridge, optical disk, a CD, DVD orBlu-ray, or other fixed or removable medium that is read by, written toor accessed by media drive 712. As these examples illustrate, thestorage media 714 can include a computer usable storage medium havingstored therein computer software or data.

In alternative embodiments, information storage mechanism 710 mightinclude other similar instrumentalities for allowing computer programsor other instructions or data to be loaded into computing module 700.Such instrumentalities might include, for example, a fixed or removablestorage unit 722 and an interface 720. Examples of such storage units722 and interfaces 720 can include a program cartridge and cartridgeinterface, a removable memory (for example, a flash memory or otherremovable memory module) and memory slot, a PCMCIA slot and card, andother fixed or removable storage units 722 and interfaces 720 that allowsoftware and data to be transferred from the storage unit 722 tocomputing module 700.

Computing module 700 might also include a communications interface 724.Communications interface 724 might be used to allow software and data tobe transferred between computing module 700 and external devices.Examples of communications interface 724 might include a modem orsoftmodem, a network interface (such as an Ethernet, network interfacecard, WiMedia, IEEE 802.XX or other interface), a communications port(such as for example, a USB port, IR port, RS232 port Bluetooth®interface, or other port), or other communications interface. Softwareand data transferred via communications interface 724 might typically becarried on signals, which can be electronic, electromagnetic (whichincludes optical) or other signals capable of being exchanged by a givencommunications interface 724. These signals might be provided tocommunications interface 724 via a channel 728. This channel 728 mightcarry signals and might be implemented using a wired or wirelesscommunication medium. Some examples of a channel might include a phoneline, a cellular link, an RF link, an optical link, a network interface,a local or wide area network, and other wired or wireless communicationschannels.

In this document, the terms “computer program medium” and “computerusable medium” are used to generally refer to media such as, forexample, memory 708, storage unit 720, media 714, and channel 728. Theseand other various forms of computer program media or computer usablemedia may be involved in carrying one or more sequences of one or moreinstructions to a processing device for execution. Such instructionsembodied on the medium, are generally referred to as “computer programcode” or a “computer program product” (which may be grouped in the formof computer programs or other groupings). When executed, suchinstructions might enable the computing module 700 to perform featuresor functions of the present invention as discussed herein.

While various embodiments of the present invention have been describedabove, it should be understood that they have been presented by way ofexample only, and not of limitation. Likewise, the various diagrams maydepict an example architectural or other configuration for theinvention, which is done to aid in understanding the features andfunctionality that can be included in the invention. The invention isnot restricted to the illustrated example architectures orconfigurations, but the desired features can be implemented using avariety of alternative architectures and configurations. Indeed, it willbe apparent to one of skill in the art how alternative functional,logical or physical partitioning and configurations can be implementedto implement the desired features of the present invention. Also, amultitude of different constituent module names other than thosedepicted herein can be applied to the various partitions. Additionally,with regard to flow diagrams, operational descriptions and methodclaims, the order in which the steps are presented herein shall notmandate that various embodiments be implemented to perform the recitedfunctionality in the same order unless the context dictates otherwise.

Although the invention is described above in terms of various exemplaryembodiments and implementations, it should be understood that thevarious features, aspects and functionality described in one or more ofthe individual embodiments are not limited in their applicability to theparticular embodiment with which they are described, but instead can beapplied, alone or in various combinations, to one or more of the otherembodiments of the invention, whether or not such embodiments aredescribed and whether or not such features are presented as being a partof a described embodiment. Thus, the breadth and scope of the presentinvention should not be limited by any of the above-described exemplaryembodiments.

Terms and phrases used in this document, and variations thereof, unlessotherwise expressly stated, should be construed as open ended as opposedto limiting. As examples of the foregoing: the term “including” shouldbe read as meaning “including, without limitation” or the like; the term“example” is used to provide exemplary instances of the item indiscussion, not an exhaustive or limiting list thereof; the terms “a” or“an” should be read as meaning “at least one,” “one or more” or thelike; and adjectives such as “conventional,” “traditional,” “normal,”“standard,” “known” and terms of similar meaning should not be construedas limiting the item described to a given time period or to an itemavailable as of a given time, but instead should be read to encompassconventional, traditional, normal, or standard technologies that may beavailable or known now or at any time in the future. Likewise, wherethis document refers to technologies that would be apparent or known toone of ordinary skill in the art, such technologies encompass thoseapparent or known to the skilled artisan now or at any time in thefuture.

The presence of broadening words and phrases such as “one or more,” “atleast,” “but not limited to” or other like phrases in some instancesshall not be read to mean that the narrower case is intended or requiredin instances where such broadening phrases may be absent. The use of theterm “module” does not imply that the components or functionalitydescribed or claimed as part of the module are all configured in acommon package. Indeed, any or all of the various components of amodule, whether control logic or other components, can be combined in asingle package or separately maintained and can further be distributedin multiple groupings or packages or across multiple locations.

Additionally, the various embodiments set forth herein are described interms of exemplary block diagrams, flow charts and other illustrations.As will become apparent to one of ordinary skill in the art afterreading this document, the illustrated embodiments and their variousalternatives can be implemented without confinement to the illustratedexamples. For example, block diagrams and their accompanying descriptionshould not be construed as mandating a particular architecture orconfiguration.

What is claimed is:
 1. A system platform, comprising: a computer systemcomprising: a non-transitory computer-readable storage medium; acomputer program product executable by a computer embodied on thenon-transitory computer-readable storage medium; wherein the computerprogram product comprises Commercial Off The Shelf (COTS) or open sourceshell computer-executable code and predicate logic computer-executablecode; a registry and directory of Universal Referential-Uniform ResourceLocators (UR-URL) Identifier Method identity elements, the registry anddirectory being stored on the non-transitory computer-readable storagemedium and taking the form of a graph database comprising a table havinga plurality of rows and columns; and a unitary shell, comprising autility platform that facilitates code writing with COTS or Open Sourceprogramming languages and object-oriented approaches, the unitary shellbeing stored on the non-transitory computer-readable storage medium;wherein the COTS or open source shell computer-executable code andpredicate logic computer-executable code are configured to employ theUR-URL Identifier Method identity elements as programmatic variables insentences, concept graphs, n-tuples, and spreadsheet functions.
 2. Acomputer implemented method, comprising: storing a registry anddirectory of Universal Referential-Uniform Resource Locators (UR-URL)Identifier Method identity elements on a non-transitorycomputer-readable storage medium; configuring the registry and directoryas a graph database, the graph database comprising a table having aplurality of rows and columns; representing the UR-URL Identity Methodidentity elements as graph nodes in various event statements anddiagrammatic forms with edges and properties specified in the fields ofresource description framework as codes and values, where codes areclass, category, and type labels drawn from an ontology and values areobject-specific properties and attributes; facilitating, by a unitaryshell comprising a utility platform stored in the non-transitorycomputer-readable storage medium, code writing with Commercial Off TheShelf (COTS) or Open Source programming languages and object-orientedapproaches; and employing the UR-URL Identifier Method identity elementsas programmatic variables in sentences, concept graphs, n-tuples, andspreadsheet functions.